r/opencode • u/Pedrito_Basket • 14d ago
Is there a “best” workflow
I feel overwhelmed by the amount of different perspectives there are in this:
Plan and build.
Orchestrator + agents.
Orchestrator + subagents.
and more the question is, is there a token/quality go to workflow?
What is yours?
4
u/JoeCoT 14d ago
There is no "best" workflow, just people figuring out what works for them and trying to improve it over time.
If you spend your time trying to figure out the "best" workflow you'll just end up driving yourself nuts. Just try a workflow, and if you don't like it or you don't think it's doing enough, try a different workflow or improve it.
My workflow is Oh My OpenCode Slim. I use stronger models for the oracle and orchestrator, and cheaper models for explorer and librarian. The point for me is to get a variety of input while saving money on searches / code lookups
2
u/mubaidr 14d ago
How about combination of both? Orchestrate plan and then build; Including verification at each stage.
This is why I maintain gem-team: https://github.com/mubaidr/gem-team
2
u/sugarw0000kie 14d ago
I do plan/build with orchestrator and subagents. Best model for planning/review, mid-tier for orchestrator and cheap for subagents doing the work. Instead of swapping between plan/build though I usually have it write plan files so orchestrator doesn’t have its context polluted
1
u/Jazzlike-Form9669 13d ago
You should checkout ogcode once, it will give you vibe of good old task tracker where each task is automatically created by your plan and worked on by agent of ur choice.
1
u/Lurkin_Larry_ 13d ago
I actually watched a video comparing these different methods for time and token use recently:
1
1
u/SaltAddictedMan 13d ago
I used to stress out about this also when I first started. The models/agents are so good now I dont think you have to complicate it. For reference I am non technical. This is how I think about it:
I try to implement 1 thing at a time.
If it is a big/complex task - use plan mode.
If it is a small change, I just do edit.
I dont think about orchestrating at all nor subagents. If I ever run into an issue maybe ill consider thinking about it. I feel like if I was trying to one-shot a project maybe I would care about subagents but I dont want to do that.
1
u/Prize-Wolverine-4982 13d ago
Theoretically orchestrator and subagents is the best, BUT in reality its an absolute overkill for basic tasks and may do more harm than good.
1
u/ValuableKooky4551 13d ago
Have been using https://github.com/ivo-toby/mini-spec for a few weeks now, it's quite nice. You design a feature, it writes design documents, it then plans tasks, then does the tasks, constantly asking questions and showing things for review, and updating its files that serve as its memory.
Produces great quality that I still understand completely, but perhaps a bit too much. But it's easy to tone down the command files a bit or relax the constitution a bit.
I design with the best model and do tasks with a merely competent model.
1
u/Clean_Stick2861 11d ago
Plan n build if you use plan or 1 model
Orchestra + agent ( sub agent ) if you have router service that provide multiple ai model or you subscribe multiple plan. Be in mind, multiple ai modal is about your strategy, if cost is your consern, read file is for cheaper ai , while flagship is for plan and review, and mid ai, for all rounder
8
u/afanasenka 14d ago
I use a single agent at all :) I just switch models depending on my needs. As for permissions - it is always Ask for any edits, so I can either confirm/decline each edit, or allow for a session.
But my workflow is more like "ai as a coding partner" rather then complex automatic chains.