Subagent Driven Development
2026-03-27
新闻来源:网淘吧
围观:18
电脑广告
手机广告
子代理驱动开发
通过为每个任务分配新的子代理来执行计划,每个任务后进行两阶段评审:先进行规范符合性评审,再进行代码质量评审。
核心原则:每个任务使用新的子代理 + 两阶段评审(先规范后质量)= 高质量、快速迭代
使用时机
digraph when_to_use {
"Have implementation plan?" [shape=diamond];
"Tasks mostly independent?" [shape=diamond];
"Stay in this session?" [shape=diamond];
"subagent-driven-development" [shape=box];
"executing-plans" [shape=box];
"Manual execution or brainstorm first" [shape=box];
"Have implementation plan?" -> "Tasks mostly independent?" [label="yes"];
"Have implementation plan?" -> "Manual execution or brainstorm first" [label="no"];
"Tasks mostly independent?" -> "Stay in this session?" [label="yes"];
"Tasks mostly independent?" -> "Manual execution or brainstorm first" [label="no - tightly coupled"];
"Stay in this session?" -> "subagent-driven-development" [label="yes"];
"Stay in this session?" -> "executing-plans" [label="no - parallel session"];
}
相较于执行计划(并行会话):
- 相同会话(无需上下文切换)
- 每个任务使用新的子代理(无上下文污染)
- 每个任务后进行两阶段评审:先规范符合性,再代码质量
- 更快迭代(任务间无需人工介入)
流程
digraph process {
rankdir=TB;
subgraph cluster_per_task {
label="Per Task";
"Dispatch implementer subagent (./implementer-prompt.md)" [shape=box];
"Implementer subagent asks questions?" [shape=diamond];
"Answer questions, provide context" [shape=box];
"Implementer subagent implements, tests, commits, self-reviews" [shape=box];
"Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)" [shape=box];
"Spec reviewer subagent confirms code matches spec?" [shape=diamond];
"Implementer subagent fixes spec gaps" [shape=box];
"Dispatch code quality reviewer subagent (./code-quality-reviewer-prompt.md)" [shape=box];
"Code quality reviewer subagent approves?" [shape=diamond];
"Implementer subagent fixes quality issues" [shape=box];
"Mark task complete in TodoWrite" [shape=box];
}
"Read plan, extract all tasks with full text, note context, create TodoWrite" [shape=box];
"More tasks remain?" [shape=diamond];
"Dispatch final code reviewer subagent for entire implementation" [shape=box];
"Use superpowers:finishing-a-development-branch" [shape=box style=filled fillcolor=lightgreen];
"Read plan, extract all tasks with full text, note context, create TodoWrite" -> "Dispatch implementer subagent (./implementer-prompt.md)";
"Dispatch implementer subagent (./implementer-prompt.md)" -> "Implementer subagent asks questions?";
"Implementer subagent asks questions?" -> "Answer questions, provide context" [label="yes"];
"Answer questions, provide context" -> "Dispatch implementer subagent (./implementer-prompt.md)";
"Implementer subagent asks questions?" -> "Implementer subagent implements, tests, commits, self-reviews" [label="no"];
"Implementer subagent implements, tests, commits, self-reviews" -> "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)";
"Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)" -> "Spec reviewer subagent confirms code matches spec?";
"Spec reviewer subagent confirms code matches spec?" -> "Implementer subagent fixes spec gaps" [label="no"];
"Implementer subagent fixes spec gaps" -> "Dispatch spec reviewer subagent (./spec-reviewer-prompt.md)" [label="re-review"];
"Spec reviewer subagent confirms code matches spec?" -> "Dispatch code quality reviewer subagent (./code-quality-reviewer-prompt.md)" [label="yes"];
"Dispatch code quality reviewer subagent (./code-quality-reviewer-prompt.md)" -> "Code quality reviewer subagent approves?";
"Code quality reviewer subagent approves?" -> "Implementer subagent fixes quality issues" [label="no"];
"Implementer subagent fixes quality issues" -> "Dispatch code quality reviewer subagent (./code-quality-reviewer-prompt.md)" [label="re-review"];
"Code quality reviewer subagent approves?" -> "Mark task complete in TodoWrite" [label="yes"];
"Mark task complete in TodoWrite" -> "More tasks remain?";
"More tasks remain?" -> "Dispatch implementer subagent (./implementer-prompt.md)" [label="yes"];
"More tasks remain?" -> "Dispatch final code reviewer subagent for entire implementation" [label="no"];
"Dispatch final code reviewer subagent for entire implementation" -> "Use superpowers:finishing-a-development-branch";
}
提示模板
./implementer-prompt.md- 分配实现者子代理./spec-reviewer-prompt.md- 分配规范符合性评审者子代理./code-quality-reviewer-prompt.md- 分配代码质量评审者子代理
示例工作流
You: I'm using Subagent-Driven Development to execute this plan.
[Read plan file once: docs/plans/feature-plan.md]
[Extract all 5 tasks with full text and context]
[Create TodoWrite with all tasks]
Task 1: Hook installation script
[Get Task 1 text and context (already extracted)]
[Dispatch implementation subagent with full task text + context]
Implementer: "Before I begin - should the hook be installed at user or system level?"
You: "User level (~/.config/superpowers/hooks/)"
Implementer: "Got it. Implementing now..."
[Later] Implementer:
- Implemented install-hook command
- Added tests, 5/5 passing
- Self-review: Found I missed --force flag, added it
- Committed
[Dispatch spec compliance reviewer]
Spec reviewer: ✅ Spec compliant - all requirements met, nothing extra
[Get git SHAs, dispatch code quality reviewer]
Code reviewer: Strengths: Good test coverage, clean. Issues: None. Approved.
[Mark Task 1 complete]
Task 2: Recovery modes
[Get Task 2 text and context (already extracted)]
[Dispatch implementation subagent with full task text + context]
Implementer: [No questions, proceeds]
Implementer:
- Added verify/repair modes
- 8/8 tests passing
- Self-review: All good
- Committed
[Dispatch spec compliance reviewer]
Spec reviewer: ❌ Issues:
- Missing: Progress reporting (spec says "report every 100 items")
- Extra: Added --json flag (not requested)
[Implementer fixes issues]
Implementer: Removed --json flag, added progress reporting
[Spec reviewer reviews again]
Spec reviewer: ✅ Spec compliant now
[Dispatch code quality reviewer]
Code reviewer: Strengths: Solid. Issues (Important): Magic number (100)
[Implementer fixes]
Implementer: Extracted PROGRESS_INTERVAL constant
[Code reviewer reviews again]
Code reviewer: ✅ Approved
[Mark Task 2 complete]
...
[After all tasks]
[Dispatch final code-reviewer]
Final reviewer: All requirements met, ready to merge
Done!
优势
相较于手动执行:
- 子代理自然遵循测试驱动开发(TDD)
- 每项任务都有全新上下文(无混淆)
- 并行安全(子代理互不干扰)
- 子代理可在工作前及工作中提问
相较于执行计划:
- 同一会话(无需交接)
- 持续进展(无需等待)
- 自动设立审查检查点
效率提升:
- 无文件读取开销(控制器提供完整文本)
- 控制器精准筛选所需上下文
- 子代理预先获取完整信息
- 问题在工作开始前即被提出(而非之后)
质量关卡:
- 自检机制在交接前发现问题
- 两阶段审查:规范符合性审查 → 代码质量审查
- 审查循环确保修复切实有效
- 规范符合性机制防止过度构建或构建不足
- 代码质量确保实现过程构建完善
成本:
- 更多子代理调用(每个任务需执行者+2名评审员)
- 控制器需进行更多准备工作(预先提取所有任务)
- 评审循环增加迭代次数
- 但能及早发现问题(比后期调试成本更低)
红色警戒项
严禁:
- 未经用户明确同意即在主分支上开始实施
- 跳过评审环节(规范符合性评审或代码质量评审)
- 对未修复的问题继续推进
- 并行分派多个实施子代理(会导致冲突)
- 让子代理读取计划文件(应直接提供完整文本)
- 省略场景设定背景(子代理需要理解任务所处环境)
- 忽视子代理提问(必须在允许其继续前回答问题)
- 在规范符合性上接受"基本达标"(规范评审发现的问题即代表未完成)
- 跳过评审循环(评审发现的问题需执行者修复后重新评审)
- 让实施者自我评审代替实际评审(两者都需要)
- 在规范符合性✅之前开始代码质量评审(错误的顺序)
- 在任一评审存在未解决问题时,转向下一任务
如果子代理提问:
- 清晰且完整地回答
- 必要时提供额外上下文
- 不要催促他们进入实施阶段
如果评审者发现问题:
- 实施者(同一子代理)进行修复
- 评审者再次评审
- 重复直至通过
- 不要跳过重新评审
如果子代理任务失败:
- 派遣修复子代理并附带具体指令
- 不要尝试手动修复(避免上下文污染)
集成
所需工作流技能:
- 超能力:使用git-worktrees- 必需:在开始前设置隔离的工作空间
- 超能力:编写计划- 创建此技能执行的计划
- 超能力:请求代码审查- 为审查者子代理提供的代码审查模板
- 超能力:完成开发分支- 在所有任务完成后完成开发
子代理应使用:
- 超能力:测试驱动开发- 子代理为每个任务遵循测试驱动开发
替代工作流程:
- 超能力:执行计划- 用于并行会话而非同一会话执行
文章底部电脑广告
手机广告位-内容正文底部


微信扫一扫,打赏作者吧~