Doc-First Workflow Replaces Plan Mode for Complex Coding Tasks
The workflow shows how to use a review document to transfer context across multiple agents like Opus and Fable, a practical alternative to plan mode that any developer using coding assistants can adopt today.
The author skips plan mode and instead has a technical design document written before coding complex tasks. A model called Fable writes the document covering technical details and verification steps, then Claude Opus implements it in a follow-up step. After implementation, a new session has Fable verify the work against the document, and important documents are kept and updated. In some cases the author uses GPT-6 Pro in ChatGPT web to access the repo and write the design doc, which Fable then reviews before Opus executes.
我不用 plan 模式，但是我复杂一点的会先写技术方案文档，主要是： 1. 人看看文档确保大方向有没有问题 2. Fable 写文档，文档里面写清楚技术细节和如何验证，后续 Opus 执行 3. 作为后续验收的依据，Opus 实施完，在新会话让 Fable 按照文档去验收一下 4. 一些重要文档会留档，但会保持更新 5. 有时候会在 ChatGPT 网页版用 GPT-6 Pro 访问 Repo 写技术方案文档，下载下来让 Fable 去审查再让 Opus 执行 简单来说，重点不是用 plan mode，但是用一个文档让人可以确认方向，以及后续多 Agent 协作传递上下文是很有价值的 pippingg @Suyanzhenq 无论是Opus，还是Sol，Astra编程方面都相当强悍，现在还有人用plan模式先规划再编程吗？ 🔗 View Quoted Tweet 💬 12 🔄 7 ❤️ 64 👀 15705 📊 22 ⚡
