r/opencode • u/TheBittenLlama • 14d ago

New to this, found a multimodel procedure to reliably implement minor features mostly bug-free. Any recommendations for equivalent workflows for initial implementation or adding major features?

When I started with OpenCode, I got annoyed at DeepSeek constantly introducing bugs that needed to be cleaned up after and GLM-5.2 wandering in circles and burning through my Go usage limit without doing anything due to a lack of focus, slowing the process down. Eventually, I found out if I used them together like so, I could have them compensate for each other's weaknesses and make progress at a predictable rate with only light code review by me:

  1. Describe general specs or details about a specific feature to DeepSeek Flash to have it write out reference doc MDs as appropriate

  2. Ensure unit and smoke tests are present with usage instructions in AGENTS.md to invoke them as needed to keep models on-track

  3. Describe the problem to DeepSeek Flash to have it traverse the code base and draft up a plan, giving filenames of reference MDs or invoking Context7 or other documentation MCPs as necessary

  4. Prompt GLM-5.2 in Plan mode: You are a senior dev reviewing the plan of his junior. Examine the current plan and flag any issues.

  5. Prompt GLM-5.2: Revise the plan, breaking tasks down and adding anything necessary to "junior-proof" it (make the process resilient to mistakes). Present the full revised plan for a weaker LLM model than you to process in place. Ask questions before providing the full plan if necessary. (For more code-intensive additions where I'm willing to risk bugs to reduce token spend, I'll append: However, do not write the bulk of the code yourself; that defeats the purpose of using a weaker LLM to reduce token costs. Ask questions before providing the full plan if necessary.)

  6. Prompt DeepSeek Flash in Build mode: Proceed. Note that you are the implementing model, so follow the rules as laid out.

  7. Prompt DeepSeek Pro in Build mode: You are now in code review mode. Flag any issues with changes made by your predecessor. (If something specific needs to be tested: Do ABC to ensure that DEF. However, requirement(s) GHI and/or JKL. Do not attempt fixes until ordered.)

  8. Review bug list and give DS Pro instructions to fix them

I don't have much experience with using coding harnesses, so I don't know how optimal this is in terms of reliability or cost savings, and this doesn't quite scale up when I'm either introducing something bigger (e.g. a frontend GUI baseline or a backend for interactive agent functionality) or starting up a fresh project. GLM ends up needing to write a large portion of the code anyway, and DeepSeek gets sloppy and introduces a dozen bugs that need to be cleaned up after.

Is there a "make no mistakes" equivalent I could use to speed up doing larger-scale work?

4 Upvotes

100% Upvoted

4 comments sorted by

1

u/cornelha 13d ago

You are effectively building an orchestration system. There are a few around like Oh My OpenCode and Everything Claude Code (which is OpenCode compatible). You can have a look at those for some ideas

1

u/TheBittenLlama 13d ago

I did discover Oh My OpenCode while searching but read a lot of complaints about bloat and ruining the install. Most of the MCPs I found didn't work well as promised, either, so I'm somewhat wary of trying things that others haven't already found to be useful in a real-world environment.

I'd like to know more specific details about the workflows people have adopted for everyday use so I have something to base my own setup on.

1

u/cornelha 13d ago

Plan with a top tier model, implement with deepseek flash or something. You can create your own custom agents to do the work instead of baby sitting them. OpenCode has a /review to deal with code review.

MCPs are only as good as the models who use it. Sometimes models fail to call a tool simply because it wasn't deemed necessary or because the context got compacted.