Plan docs over plan mode: Fable writes the spec, Opus executes, Fable validates
dotey · x · 2026-09-23
@dotey quotes @xicilion to share a practical multi-agent coding workflow: the key isn't plan mode, but a written spec document that fixes direction, carries context, and enables multi-agent collaboration.
@xicilion's four reasons for writing plans:
- Build consensus: one sentence can't capture a goal; details shape the architecture
- Sync context: the AI gathers info around the goal and exposes existing gaps
- Lock the path: AI drifts from the goal while solving subproblems, causing rework
- Record progress: working docs must be continuously updated
@dotey's concrete loop:
- Write a tech spec doc first; human reviews the overall direction
- Have Fable write the doc (with technical details and validation criteria), then hand it to Opus to implement
- After implementation, start a fresh session and have Fable validate against the doc
- Archive important docs and keep them updated
- For complex specs, use GPT-6 Pro in ChatGPT's web UI with repo access, then have Fable review and Opus execute
Related event: Developers Favor Spec Documents Over Plan Mode for AI Coding(4 posts)→
More from coding & agent
- YouArt Desktop launches: AI agent edits video in CapCut, DaVinci and Premiere from client feedback — mhdfaran · 2026-11-11
- Boubou: one-command local voice AI that serves your phone and robots over Wi-Fi — LuozhuZhang · 2026-11-11
- Python 3.15 makes AttributeError actionable: suggests .append for .push mix-ups — KhuyenTran16 · 2026-11-11
- sentence-transformers maintainer releases new embedding pooling training method, code & checkpoints — tomaarsen · 2026-11-11
- droid-mcp turns your Android phone into an MCP server with 160+ tools for Claude Code — zvone1122 · 2026-11-11
- The decade of agents: simulate real customers to test your agent before launch — EXM7777 · 2026-11-11