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.
Related event: Developers Favor Spec Documents Over Plan Mode for AI Coding(4 posts)→
More from coding & agent
- Boubou: open-source CLI turns your laptop into a fully local voice AI hub — alexcovo_eth · 2026-11-12
- User automates entire video clipping workflow with Nous Research's Hermes agent — Teknium · 2026-11-12
- As models improve, writing good evals gets harder and more important — amankhan · 2026-11-12
- Prime agent ships with day-one multi-agent communication, runs in Minecraft unmodified — sarahcat21 · 2026-11-12
- Autonomous agent edits just 1,024 weights to lift Qwen3.5 0.8B from 7.4% to 37.4% on MATH-500 — VictorSanh · 2026-11-12
- Omarchy 4.6 lets you share local AI models across your tailnet, says DHH — alexcovo_eth · 2026-11-12