Augment Code 分享了他们如何让一个 agent 一口气完成整个设计文档实现，省去拆 ticket 和接力，适合做大项目的人参考。
Augment Code 团队在 Cosmos 项目中使用一个 worker agent 处理整个设计文档，生成单个数千行 PR。该 agent 不仅实现设计，还自行修复 CI 失败并处理审查意见，无需拆 ticket 或 agent 间交接。团队认为单 agent 持有完整上下文能产出更连贯的变更，避免分块导致的假设不一致。此方法适用于大型项目，与多数团队的小范围 agent 工作方式形成对比。
Most teams point agents at small, well-scoped work. A ticket goes in, a tidy PR comes out, a human r...
Most teams point agents at small, well-scoped work. A ticket goes in, a tidy PR comes out, a human reviews it, it merges. Our largest projects don't work that way. On Cosmos, once a human has reviewed and approved the design doc, we hand the entire design to a single worker agent and let it build the whole thing as one PR. It implements the design, fixes its own CI failures, and works through review comments until the change is ready to merge. No ticket-splitting, no relay between agents. The PRs are large, often thousands of lines, and we prefer them that way. One agent holding the full approved design writes a more coherent change than several agents each working from a slice of the context. The seams you get from splitting, the mismatched assumptions between unit three and unit seven, don't show up when one agent carries the whole picture. 💬 2 🔄 2 ❤️ 6 👀 226 📊 4 ⚡