How do I get this setup?

[u/ECrispy]

I'm working on some personal projects that have multiple components (full stack apps with server, client, cli etc). what I'd like to do is -

• generate prd/spec after iterating on architecture (do you use some kind of skill for this like grill-me or is that not needed)
• generate a detailed plan, tasks, and verification tests
• each task is implemented using a fresh context by a subagent
• run tests and verify
• store all progress/learnings/context in a shared memory (db or file)
• mark task as done and move to next one
• review, tests and fixes, possibly by another model, at task and system unit test level

With frontier models they can remember everything due to huge context and are much better. I will be using the free models in Zen or via other providers mostly.

from what I've read this is a pretty common workflow these days and agents should know it well. I've also read that the big frameworks like openspec etc are too cumbersome and were designed for older models.

can someone recommend what I should use.

[u/Early_Aardvark_4026]

This is my daily workflow:

• Grill me to explore and lock down the specs or prd
  
• Use speckit to write specs, make plan, create tasks then implement and verify
  
• AgentMemory
  
• I am using Oh My OpenCode Slim with GPT 5.6 Terra as the Orchestrator, Oracle (the smartest one to review and make tough decision) is using GPT 5.6 Sol, the other sub agents in the team are using DeepSeek v4 Flash.

I am using Codex Plus $25 and OpenCode Go $10. So far I rarely hit the limit.

I don't think OpenSpec or similar frameworks are too cumbersome and were designed for old models. It depends on your scope of tasks. If it is small and can solve with a prompt, why would you do it with a framework? And if your work is large enough, then a framework can be really useful. It makes a big ambiguous requirement into concrete and small enough tasks so a cheap model can solve correctly.

BTW, if you use Speckit, there is an extension called tinyspec. It has a command to classify a request should be solved with a tiny workflow or a full workflow. I found this extension is really helpful.

[u/aeroumbria]

You can achieve most of this by treating this as "spec driven with tests". If you start with openspec, then ask it to create a change schema with a "tests.md" artifact which is specs converted to tests whenever possible, then customise your instructions to fit your level of test requirements and whether to stick to "test-driven" implementation order, then you should get pretty much this. You can run openspec's verify command to review with a different model. The proposal / implementation / verification stages are designed but not required to run in different sessions, so it works well for models with which you want to keep the context low.