返回 Skill 列表
extension
分类: 开发与工程无需 API Key

aico-subagent-driven

通过为每个任务派遣新的子代理来执行实施计划。每个任务都包括:执行者→规格审查→质量审查。两阶段审查确保了正确性和质量。使用此技能的情况:- 有一个包含多个独立任务的实施计划- 希望在每个任务后都有质量检查门进行自动执行- 任务大多是独立的(不紧密耦合)- 用户要求“执行计划”、“运行任务”、“自动实施”前提条件:必须从aico-*-plan或aico-*-task-breakdown技能中获得计划。过程:对于每个任务:派遣执行者→规格审查(通过?)→质量审查(通过?)→下一个任务审查顺序:总是先进行规格符合性审查,然后是代码质量审查。

person作者: jakexiaohubgithub

Subagent-Driven Development

Process

1. Read plan, extract all tasks
      ↓
2. Create TodoWrite with all tasks
      ↓
3. For each task:
   a. Dispatch Implementer Subagent
   b. Implementer: implement, test, commit
   c. Dispatch Spec Reviewer (matches spec?)
   d. Spec issues? → Implementer fixes → re-review
   e. Dispatch Quality Reviewer (code quality?)
   f. Quality issues? → Implementer fixes → re-review
   g. Mark task complete
      ↓
4. All tasks complete → Final review → Done

Review Order is Critical

Spec Compliance Review FIRST
        ↓
    ✅ Passes
        ↓
Code Quality Review SECOND

Why: No point reviewing code quality if it doesn't meet spec.

Subagent Prompts

Implementer

  • Provide FULL task text (don't make subagent read file)
  • Provide context (where task fits in plan)
  • Require TDD and self-review

Spec Reviewer

  • Check: Does implementation match spec exactly?
  • Missing anything? Added anything extra?

Quality Reviewer

  • Check: Tests, readability, error handling, performance, security
  • Rate issues as Critical/Important/Minor

Key Rules

  • ALWAYS run both reviews (spec AND quality)
  • MUST fix issues before proceeding to next task
  • NEVER dispatch multiple implementers in parallel
  • ALWAYS provide full task text to subagent
  • Spec review FIRST, then quality review

Red Flags

Never:

  • Skip any review
  • Proceed with unfixed issues
  • Start quality review before spec passes
  • Move to next task with open issues

If issues found:

  • Same implementer fixes them
  • Reviewer reviews again
  • Repeat until approved

Common Mistakes

  • ❌ Skip spec review → ✅ Always verify spec first
  • ❌ Skip quality review → ✅ Always check quality
  • ❌ Wrong review order → ✅ Spec first, then quality
  • ❌ Provide partial task text → ✅ Give full text