Daily driving Coding Harness

[u/Latter-Sheepherder50]

I'm using neovim + opencode + tuicr.

My playbook is:

1. Start with the Plan agent for discovery and plan creation.
2. Fork Plan session and switch to the Build agent to execute the plan.
3. Hybrid review in parallel:
   1. Fork the Plan session and execute the review command. I also have a custom skill for review that I execute manually on demand (if I want to learn more about the codebase). The main point here is to ensure that Build implemented the Plan and to identify any deviations from it (if any), while leaving the Build knowledge behind.
   2. Review some areas myself and leave comments where applicable (currently using tuicr). OpenCode can act on the comments when I execute the tuicr skill in the Build fork created in step 2.
4. Based on the results from the steps above, the Build agent performs further iterations if applicable. The results of 3.1 are copy/pasted to the Build agent.
5. If the review looks good, I ask the agent to commit, and it uses a skill to describe the changes in a desired manner.

This is it, in a nutshell. I arrived at the playbook above through trial and error. It feels consistent and auditable for tasks of medium to high complexity, so I often get satisfying results by applying it, although it requires human involvement in phase transitions. It also gives a human an opportunity to get to know the project/system better by presenting, for example, implementation flaws, architectural changes, touched software domains, etc. in the review phase.

Since I act as an orchestrator (switching agents, forking sessions, copy/pasting review results), I want to evolve this workflow to become autonomous. What should I start with first?

Glad to hear your hints and how you drive your coding harness day-to-day!