关于 delegated-development
delegated-development 是通过为每项任务分配新的子 Agent 来执行实施计划的技能。它要求先审查规范符合性,再审查代码质量,并在继续下一项任务前完成问题修复和复审。
主要功能
- 01每项任务分配新的子 Agent
- 02先审查规范符合性
- 03再审查代码质量
- 04修复后重复审查
- 05提供任务上下文和提示模板
适用场景
- 01在单次会话中执行实施计划
- 02将工作拆分为相对独立的任务
- 03核对实现是否符合要求
- 04继续前处理审查发现的问题
安装
复制下面的命令,在终端中运行。
$
npx skills add https:/ / github.com/ qodex-ai/ ai-agent-skills --skill delegated-development安装后在 Claude Code 中输入/delegated-development确认已加载。
包含的文件
除 SKILL.md 外,安装时一起下载的参考资料和脚本。
code-quality-reviewer-prompt.mdimplementer-prompt.mdspec-reviewer-prompt.md详细介绍
子 Agent 驱动的开发
通过为每个任务分派全新的子 Agent 来执行计划,并在每个任务后进行两阶段审查:先进行规范符合性审查,再进行代码质量审查。
核心原则: 每个任务使用全新的子 Agent + 两阶段审查(先规范后质量)= 高质量、快速迭代
何时使用
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"];
}
对比执行计划(并行会话):
- 同一会话(无上下文切换)
- 每个任务使用全新的子 Agent(无上下文污染)
- 每个任务后进行两阶段审查:先规范符合性,再代码质量
- 更快的迭代(任务之间无需人工介入)
流程
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- 分派实现者子 Agent./spec-reviewer-prompt.md- 分派规范符合性审查者子 Agent./code-quality-reviewer-prompt.md- 分派代码质量审查者子 Agent
工作流示例
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!
优势
对比手动执行:
- 子 Agent 自然遵循 TDD
- 每个任务使用全新上下文(无混淆)
- 并行安全(子 Agent 之间互不干扰)
- 子 Agent 可以提问(在工作开始前及进行中)
对比执行计划:
- 同一会话(无需交接)
- 持续推进(无需等待)
- 审查检查点自动化
效率提升:
- 无文件读取开销(控制器提供完整文本)
- 控制器精确挑选所需的上下文
- 子 Agent 提前获得完整信息
- 问题在工作开始前暴露(而非之后)
质量关卡:
- 自审在交接前发现问题
- 两阶段审查:规范符合性,然后代码质量
- 审查循环确保修复真正有效
- 规范符合性防止过度/不足构建
- 代码质量确保实现构建良好
成本:
- 更多子 Agent 调用(每个任务:实现者 + 2 位审查者)
- 控制器需要更多准备工作(提前提取所有任务)
- 审查循环增加迭代次数
- 但能及早发现问题(比之后调试更便宜)
危险信号
绝不:
- 跳过审查(规范符合性或代码质量)
- 带着未修复的问题继续
- 并行分派多个实现子 Agent(冲突)
- 让子 Agent 读取计划文件(改为提供完整文本)
- 跳过场景设定上下文(子 Agent 需要理解任务所处的位置)
- 忽略子 Agent 的问题(在让其继续之前回答)
- 在规范符合性上接受“差不多就行”(规范审查者发现问题 = 未完成)
- 跳过审查循环(审查者发现问题 = 实现者修复 = 再次审查)
- 让实现者的自审替代实际审查(两者都需要)
- 在规范符合性为 ✅ 之前开始代码质量审查(顺序错误)
- 在任一审查存在未解决问题时进入下一个任务
如果子 Agent 提问:
- 清晰且完整地回答
- 如有需要,提供额外上下文
- 不要催促其进入实现
如果审查者发现问题:
- 实现者(同一子 Agent)修复它们
- 审查者再次审查
- 重复直到通过
- 不要跳过重新审查
如果子 Agent 任务失败:
- 分派修复子 Agent 并提供具体指令
- 不要尝试手动修复(上下文污染)
集成
必需的工作流技能:
- superpowers:writing-plans - 创建此技能所执行的计划
- superpowers:requesting-code-review - 供审查者子 Agent 使用的代码审查模板
- superpowers:finishing-a-development-branch - 在所有任务完成后完成开发
子 Agent 应使用:
- superpowers:test-driven-development - 子 Agent 为每个任务遵循 TDD
替代工作流:
- superpowers:executing-plans - 用于并行会话而非同会话执行
评论
支持 Markdown