subagent-driven-development

Subagent-Driven Development

来源: PDForge 类型: 协作模式型 Skill

Announce at start: "I'm using the subagent-driven-development skill to ensure high-quality implementation through fresh-context subagents and two-stage review."

Core Concept

每个任务分发给一个全新上下文的子代理执行：

• 子代理不知道其他任务的实现细节
• 子代理专注于当前任务
• 避免"上下文污染"导致的假设和捷径

每个任务完成后经过两阶段审查：

1. 规格合规审查 - 是否满足计划要求
2. 代码质量审查 - 是否符合最佳实践

Workflow

digraph skill_flow {
    rankdir=TB;
    node [shape=box];
    
    READ_PLAN [label="读取计划\n提取任务列表"];
    NEXT_TASK [label="获取下一个任务"];
    DISPATCH_IMPL [label="Dispatch\nImplementer Subagent"];
    IMPL_WORK [label="Implementer:\n遵循 TDD 实现\n自检后提交"];
    SPEC_REVIEW [label="Dispatch\nSpec Reviewer Subagent"];
    SPEC_CHECK [label="规格合规？" shape=diamond];
    QUALITY_REVIEW [label="Dispatch\nCode Quality Reviewer Subagent"];
    QUALITY_CHECK [label="质量合格？" shape=diamond];
    MARK_DONE [label="标记任务完成"];
    MORE_TASKS [label="还有任务？" shape=diamond];
    DONE [label="全部完成"];
    
    READ_PLAN -> NEXT_TASK;
    NEXT_TASK -> DISPATCH_IMPL;
    DISPATCH_IMPL -> IMPL_WORK;
    IMPL_WORK -> SPEC_REVIEW;
    SPEC_REVIEW -> SPEC_CHECK;
    SPEC_CHECK -> QUALITY_REVIEW [label="通过"];
    SPEC_CHECK -> IMPL_WORK [label="不通过\n修复"];
    QUALITY_REVIEW -> QUALITY_CHECK;
    QUALITY_CHECK -> MARK_DONE [label="通过"];
    QUALITY_CHECK -> IMPL_WORK [label="不通过\n修复"];
    MARK_DONE -> MORE_TASKS;
    MORE_TASKS -> NEXT_TASK [label="是"];
    MORE_TASKS -> DONE [label="否"];
}

Why Two-Stage Review?

单一审查常遗漏问题：

问题类型	单一审查	两阶段审查
"代码写得好但不符合规格"	❌ 常遗漏	✅ 规格审查捕获
"符合规格但代码质量差"	❌ 常遗漏	✅ 质量审查捕获
"两者都有问题"	⚠️ 可能只发现一个	✅ 分别发现

顺序不可颠倒：

1. 先确保做对的事（规格合规）
2. 再确保把事做好（代码质量）

Subagent Roles

1. Implementer (实现者)

职责：按任务规格实现代码

# 见 implementer-prompt.md
- 读取任务详情
- 遵循 TDD 实现
- 运行验证命令
- 自检后提交

2. Spec Reviewer (规格审查员)

职责：检查实现是否符合任务规格

# 见 spec-reviewer-prompt.md
- 对照任务规格检查
- 不关心代码质量
- 只关心"是否做了规格要求的事"