A while back I wrote a post called ". The repo ships an agents/ roster you dispatch, a reference/ set of deep-dives (the threading model, the parallel pipeline, the PR review cycle), and an ARCHITECTURE.md with the system diagrams. Fork it. Adapt the personas to your product's users (the domain-user-lens is a template you copy once per persona), swap in your test runner, your CI, and your code-review bot, and make it yours. The framework-specific details are stripped out; the methodology is language- and stack-agnostic.
If you want the single-skill, one-disciplined-developer version, the original /wizard, it's preserved at the v1 git tag and still works. Start there if a team feels like more than you need. A lot of people will never want more than the solo architect, and that's a completely reasonable place to live.
And if you haven't read it, the original post that started all this, "I Made Claude Code Think Before It Codes. Here's the Prompt.", is the foundation everything above is built on. v2 is just what happens when you take one disciplined developer and ask: what if there were a whole team of them, an agent to turn ideas into issues, and someone to conduct the whole thing?
Now go build something while you sleep.
SOCIAL SHARE CARD GENERATOR