dotey shares doc-driven multi-agent coding workflow: Fable writes spec, Opus executes
dotey · x · 2026-09-22
Responding to a question about whether people still use plan mode before coding, dotey shares his doc-driven workflow that doesn't rely on plan mode:
- A human reviews the spec document first to confirm direction;
- Fable writes the doc with technical details and validation steps, then Opus implements;
- The doc doubles as acceptance criteria: after implementation, Fable verifies against it in a fresh session;
- Important docs are archived and kept up to date;
- He sometimes uses GPT-6 Pro in ChatGPT web with repo access to write specs, then has Fable review and Opus execute.
His takeaway: the key isn't plan mode but using documents for human direction-checking and context passing across agents.
More from coding & agent
- Virtual Biotech teardown: 6 design decisions behind Science's 37,000-agent drug company — bravo_abad · 2026-09-22
- Half of 25 PM Job Openings Ask for Evals Experience; Ramp, Shopify, Harvey, Cursor Share ROI Data — lennysan · 2026-09-22
- 37,000-agent virtual drug company: the engineering behind Virtual Biotech — bravo_abad · 2026-09-22
- LinearSolveBench debuts: testing if AI can write fast C solvers for sparse linear systems — hgarud · 2026-09-22
- Navier-Stokes partial regularity machine-checked in Lean by 50-agent swarm in 36 hours — RexDouglass · 2026-09-22
- 5 open-source repos that teach your agents what models can't — 0xsachi · 2026-09-22