Back to Details

teams-driven-development

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Teams-Driven Development

团队驱动开发（Teams-Driven Development）

Execute plan by delegating fresh worker per task via 
teams delegate
, with two-stage review after each: spec compliance review first, then code quality review.
Core principle: Fresh worker per task + two-stage review (spec then quality) = high quality, fast iteration
通过
teams delegate
为每个任务分配专属worker来执行计划，每个任务完成后需经过两阶段审查：首先是规范合规性审查，然后是代码质量审查。
核心原则： 每个任务分配专属worker + 两阶段审查（规范审查→质量审查）= 高质量、快速迭代

When to Use

适用场景

dot
digraph when_to_use {
    "Have implementation plan?" [shape=diamond];
    "Tasks mostly independent?" [shape=diamond];
    "Stay in this session?" [shape=diamond];
    "teams-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?" -> "teams-driven-development" [label="yes"];
    "Stay in this session?" -> "executing-plans" [label="no - parallel session"];
}
vs. Executing Plans (parallel session):
  • Same session (no context switch)
  • Fresh worker per task (no context pollution)
  • Two-stage review after EACH task: spec compliance first, then code quality
  • Faster iteration (no human-in-loop between tasks)
dot
digraph when_to_use {
    "Have implementation plan?" [shape=diamond];
    "Tasks mostly independent?" [shape=diamond];
    "Stay in this session?" [shape=diamond];
    "teams-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?" -> "teams-driven-development" [label="yes"];
    "Stay in this session?" -> "executing-plans" [label="no - parallel session"];
}
与“执行计划（并行会话）”的对比：
  • 同一会话（无需上下文切换）
  • 每个任务分配专属worker（无上下文污染）
  • 每个任务完成后均需经过两阶段审查：先规范合规性，后代码质量
  • 迭代速度更快（任务间无需人工介入）

The Process

执行流程

dot
digraph process {
    rankdir=TB;

    subgraph cluster_per_task {
        label="Per Task";
        "Delegate to implementer worker (./implementer-prompt.md)" [shape=box];
        "Implementer worker asks questions?" [shape=diamond];
        "Answer questions, provide context" [shape=box];
        "Implementer worker implements, tests, commits, self-reviews" [shape=box];
        "Delegate to spec reviewer worker (./spec-reviewer-prompt.md)" [shape=box];
        "Spec reviewer worker confirms code matches spec?" [shape=diamond];
        "Create `tk` tickets for all surfaced issues. Implementer worker fixes spec gaps" [shape=box];
        "Delegate to code quality reviewer worker (./code-quality-reviewer-prompt.md)" [shape=box];
        "Code quality reviewer worker approves?" [shape=diamond];
        "Create `tk` tickets for all surfaced issues. Implementer worker fixes quality issues" [shape=box];
        "Mark task complete in TodoWrite" [shape=box];
    }

    "Read plan ticket, extract all tasks with full text, note context, create TodoWrite" [shape=box];
    "More tasks remain?" [shape=diamond];
    "Delegate to final code reviewer worker for entire implementation" [shape=box];
    "Use superpowers:finishing-a-development-branch" [shape=box style=filled fillcolor=lightgreen];

    "Read plan ticket, extract all tasks with full text, note context, create TodoWrite" -> "Delegate to implementer worker (./implementer-prompt.md)";
    "Delegate to implementer worker (./implementer-prompt.md)" -> "Implementer worker asks questions?";
    "Implementer worker asks questions?" -> "Answer questions, provide context" [label="yes"];
    "Answer questions, provide context" -> "Delegate to implementer worker (./implementer-prompt.md)";
    "Implementer worker asks questions?" -> "Implementer worker implements, tests, commits, self-reviews" [label="no"];
    "Implementer worker implements, tests, commits, self-reviews" -> "Delegate to spec reviewer worker (./spec-reviewer-prompt.md)";
    "Delegate to spec reviewer worker (./spec-reviewer-prompt.md)" -> "Spec reviewer worker confirms code matches spec?";
    "Spec reviewer worker confirms code matches spec?" -> "Create `tk` tickets for all surfaced issues. Implementer worker fixes spec gaps" [label="no"];
    "Create `tk` tickets for all surfaced issues. Implementer worker fixes spec gaps" -> "Delegate to spec reviewer worker (./spec-reviewer-prompt.md)" [label="re-review"];
    "Spec reviewer worker confirms code matches spec?" -> "Delegate to code quality reviewer worker (./code-quality-reviewer-prompt.md)" [label="yes"];
    "Delegate to code quality reviewer worker (./code-quality-reviewer-prompt.md)" -> "Code quality reviewer worker approves?";
    "Code quality reviewer worker approves?" -> "Create `tk` tickets for all surfaced issues. Implementer worker fixes quality issues" [label="no"];
    "Create `tk` tickets for all surfaced issues. Implementer worker fixes quality issues" -> "Delegate to code quality reviewer worker (./code-quality-reviewer-prompt.md)" [label="re-review"];
    "Code quality reviewer worker approves?" -> "Mark task complete in TodoWrite" [label="yes"];
    "Mark task complete in TodoWrite" -> "More tasks remain?";
    "More tasks remain?" -> "Delegate to implementer worker (./implementer-prompt.md)" [label="yes"];
    "More tasks remain?" -> "Delegate to final code reviewer worker for entire implementation" [label="no"];
    "Delegate to final code reviewer worker for entire implementation" -> "Use superpowers:finishing-a-development-branch";
}
dot
digraph process {
    rankdir=TB;

    subgraph cluster_per_task {
        label="Per Task";
        "Delegate to implementer worker (./implementer-prompt.md)" [shape=box];
        "Implementer worker asks questions?" [shape=diamond];
        "Answer questions, provide context" [shape=box];
        "Implementer worker implements, tests, commits, self-reviews" [shape=box];
        "Delegate to spec reviewer worker (./spec-reviewer-prompt.md)" [shape=box];
        "Spec reviewer worker confirms code matches spec?" [shape=diamond];
        "Create `tk` tickets for all surfaced issues. Implementer worker fixes spec gaps" [shape=box];
        "Delegate to code quality reviewer worker (./code-quality-reviewer-prompt.md)" [shape=box];
        "Code quality reviewer worker approves?" [shape=diamond];
        "Create `tk` tickets for all surfaced issues. Implementer worker fixes quality issues" [shape=box];
        "Mark task complete in TodoWrite" [shape=box];
    }

    "Read plan ticket, extract all tasks with full text, note context, create TodoWrite" [shape=box];
    "More tasks remain?" [shape=diamond];
    "Delegate to final code reviewer worker for entire implementation" [shape=box];
    "Use superpowers:finishing-a-development-branch" [shape=box style=filled fillcolor=lightgreen];

    "Read plan ticket, extract all tasks with full text, note context, create TodoWrite" -> "Delegate to implementer worker (./implementer-prompt.md)";
    "Delegate to implementer worker (./implementer-prompt.md)" -> "Implementer worker asks questions?";
    "Implementer worker asks questions?" -> "Answer questions, provide context" [label="yes"];
    "Answer questions, provide context" -> "Delegate to implementer worker (./implementer-prompt.md)";
    "Implementer worker asks questions?" -> "Implementer worker implements, tests, commits, self-reviews" [label="no"];
    "Implementer worker implements, tests, commits, self-reviews" -> "Delegate to spec reviewer worker (./spec-reviewer-prompt.md)";
    "Delegate to spec reviewer worker (./spec-reviewer-prompt.md)" -> "Spec reviewer worker confirms code matches spec?";
    "Spec reviewer worker confirms code matches spec?" -> "Create `tk` tickets for all surfaced issues. Implementer worker fixes spec gaps" [label="no"];
    "Create `tk` tickets for all surfaced issues. Implementer worker fixes spec gaps" -> "Delegate to spec reviewer worker (./spec-reviewer-prompt.md)" [label="re-review"];
    "Spec reviewer worker confirms code matches spec?" -> "Delegate to code quality reviewer worker (./code-quality-reviewer-prompt.md)" [label="yes"];
    "Delegate to code quality reviewer worker (./code-quality-reviewer-prompt.md)" -> "Code quality reviewer worker approves?";
    "Code quality reviewer worker approves?" -> "Create `tk` tickets for all surfaced issues. Implementer worker fixes quality issues" [label="no"];
    "Create `tk` tickets for all surfaced issues. Implementer worker fixes quality issues" -> "Delegate to code quality reviewer worker (./code-quality-reviewer-prompt.md)" [label="re-review"];
    "Code quality reviewer worker approves?" -> "Mark task complete in TodoWrite" [label="yes"];
    "Mark task complete in TodoWrite" -> "More tasks remain?";
    "More tasks remain?" -> "Delegate to implementer worker (./implementer-prompt.md)" [label="yes"];
    "More tasks remain?" -> "Delegate to final code reviewer worker for entire implementation" [label="no"];
    "Delegate to final code reviewer worker for entire implementation" -> "Use superpowers:finishing-a-development-branch";
}

Prompt Templates

提示模板

  • ./implementer-prompt.md
    - Delegate to implementer worker
  • ./spec-reviewer-prompt.md
    - Delegate to spec compliance reviewer worker
  • ./code-quality-reviewer-prompt.md
    - Delegate to code quality reviewer worker
  • ./implementer-prompt.md
    - 分配给实现worker的提示模板
  • ./spec-reviewer-prompt.md
    - 分配给规范合规性审查worker的提示模板
  • ./code-quality-reviewer-prompt.md
    - 分配给代码质量审查worker的提示模板

How to Delegate

分配方式

Use 
teams delegate
for each worker:
teams(action: 'delegate', tasks: [
  {text: '<implementer prompt with full task text + context>', assignee: 'implementer-task-1'}
])
For reviews:
teams(action: 'delegate', tasks: [
  {text: '<spec review prompt>', assignee: 'spec-reviewer-task-1'}
])
为每个worker使用
teams delegate
命令：
teams(action: 'delegate', tasks: [
  {text: '<包含完整任务文本+上下文的实现提示>', assignee: 'implementer-task-1'}
])
审查任务的分配方式：
teams(action: 'delegate', tasks: [
  {text: '<规范审查提示>', assignee: 'spec-reviewer-task-1'}
])

Example Workflow

示例工作流

You: I'm using Teams-Driven Development to execute this plan.

[Read plan ticket once]
[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)]
[teams delegate implementer worker 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

[teams delegate spec compliance reviewer]
Spec reviewer: ✅ Spec compliant - all requirements met, nothing extra

[Get git SHAs, teams delegate 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)]
[teams delegate implementer worker with full task text + context]

Implementer: [No questions, proceeds]
Implementer:
  - Added verify/repair modes
  - 8/8 tests passing
  - Self-review: All good
  - Committed

[teams delegate spec compliance reviewer]
Spec reviewer: ❌ Issues:
  - Missing: Progress reporting (spec says "report every 100 items")
  - Extra: Added --json flag (not requested)
  - Create `tk` tickets for all surfaced issues

[Implementer fixes issues]
Implementer: Removed --json flag, added progress reporting

[Spec reviewer reviews again]
Spec reviewer: ✅ Spec compliant now

[teams delegate 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]
[teams delegate final code-reviewer]
Final reviewer: All requirements met, ready to merge

Done!
你：我正在使用团队驱动开发（Teams-Driven Development）来执行这个计划。

[阅读计划工单一次]
[提取所有5个任务的完整文本和上下文]
[在TodoWrite中创建所有任务]

任务1：钩子安装脚本

[获取任务1的文本和上下文（已提取完成）]
[通过teams delegate将任务分配给实现worker，附带完整任务文本+上下文]

实现worker：“开始之前——钩子应该安装在用户级别还是系统级别？”

你：“用户级别（~/.config/superpowers/hooks/）”

实现worker：“明白。现在开始实现...”
[稍后] 实现worker：
  - 已实现install-hook命令
  - 添加了测试，5/5全部通过
  - 自我审查：发现遗漏了--force参数，已补充
  - 已提交代码

[通过teams delegate分配给规范合规性审查worker]
规范审查worker：✅ 符合规范——所有需求均已满足，无额外内容

[获取git提交哈希，通过teams delegate分配给代码质量审查worker]
代码质量审查worker：优点：测试覆盖率良好，代码简洁。问题：无。已批准。

[标记任务1在TodoWrite中完成]

任务2：恢复模式

[获取任务2的文本和上下文（已提取完成）]
[通过teams delegate将任务分配给实现worker，附带完整任务文本+上下文]

实现worker：[无疑问，直接开始]
实现worker：
  - 添加了验证/修复模式
  - 8/8测试全部通过
  - 自我审查：无问题
  - 已提交代码

[通过teams delegate分配给规范合规性审查worker]
规范审查worker：❌ 存在问题：
  - 遗漏：进度报告（规范要求“每处理100个项目报告一次进度”）
  - 多余：添加了--json参数（未在需求中提及）
  - 为所有发现的问题创建`tk`工单

[实现worker修复问题]
实现worker：已移除--json参数，添加了进度报告功能

[规范审查worker重新审查]
规范审查worker：✅ 现在符合规范

[通过teams delegate分配给代码质量审查worker]
代码质量审查worker：优点：实现可靠。问题（重要）：存在魔法数字（100）

[实现worker修复问题]
实现worker：已将100提取为PROGRESS_INTERVAL常量

[代码质量审查worker重新审查]
代码质量审查worker：✅ 已批准

[标记任务2在TodoWrite中完成]

...

[所有任务完成后]
[通过teams delegate分配给最终代码审查worker对整个实现进行审查]
最终审查worker：所有需求均已满足，可合并

完成！

Advantages

优势

vs. Manual execution:
  • Workers follow TDD naturally
  • Fresh context per task (no confusion)
  • Parallel-safe (workers don't interfere)
  • Worker can ask questions (before AND during work)
vs. Executing Plans:
  • Same session (no handoff)
  • Continuous progress (no waiting)
  • Review checkpoints automatic
Efficiency gains:
  • No file reading overhead (controller provides full text)
  • Controller curates exactly what context is needed
  • Worker gets complete information upfront
  • Questions surfaced before work begins (not after)
Quality gates:
  • Self-review catches issues before handoff
  • Two-stage review: spec compliance, then code quality
  • Review loops ensure fixes actually work
  • Spec compliance prevents over/under-building
  • Code quality ensures implementation is well-built
Cost:
  • More worker invocations (implementer + 2 reviewers per task)
  • Controller does more prep work (extracting all tasks upfront)
  • Review loops add iterations
  • But catches issues early (cheaper than debugging later)
与手动执行的对比：
  • Worker会自然遵循测试驱动开发（TDD）流程
  • 每个任务拥有独立上下文（无混淆）
  • 支持并行执行（Worker之间不会互相干扰）
  • Worker可在工作前及工作中提出问题
与“执行计划（并行会话）”的对比：
  • 同一会话（无需交接）
  • 持续推进（无需等待）
  • 审查检查点自动化
效率提升：
  • 无文件读取开销（控制器提供完整文本）
  • 控制器精准筛选所需上下文
  • Worker可提前获取全部信息
  • 问题在工作开始前就被提出（而非之后）
质量保障：
  • 自我审查可在交接前发现问题
  • 两阶段审查：规范合规性→代码质量
  • 审查循环确保问题真正被修复
  • 规范合规性审查避免过度实现或实现不足
  • 代码质量审查确保实现的健壮性
成本说明：
  • Worker调用次数更多（每个任务需要实现worker + 2个审查worker）
  • 控制器需要更多准备工作（提前提取所有任务）
  • 审查循环会增加迭代次数
  • 但可提前发现问题（比后期调试成本更低）

Red Flags

�注意事项

NEVER:
  • Skip reviews (spec compliance OR code quality)
  • Proceed with unfixed issues
  • Delegate multiple implementer workers in parallel on the same codebase (conflicts)
  • Make worker read plan file (provide full text instead)
  • Skip scene-setting context (worker needs to understand where task fits)
  • Ignore worker questions (answer before letting them proceed)
  • Accept "close enough" on spec compliance (spec reviewer found issues = not done)
  • Skip review loops (reviewer found issues = implementer fixes = review again)
  • Let implementer self-review replace actual review (both are needed)
  • Start code quality review before spec compliance is ✅ (wrong order)
  • Move to next task while either review has open issues
If worker asks questions:
  • Answer clearly and completely
  • Provide additional context if needed
  • Don't rush them into implementation
If reviewer finds issues:
  • Implementer (same worker) fixes them
  • Reviewer reviews again
  • Repeat until approved
  • Don't skip the re-review
If worker fails task:
  • Delegate fix worker with specific instructions
  • Don't try to fix manually (context pollution)
绝对禁止：
  • 跳过审查（规范合规性或代码质量审查）
  • 带着未修复的问题继续推进
  • 在同一代码库上并行分配多个实现worker（会导致冲突）
  • 让worker自行读取计划文件（需提供完整文本）
  • 跳过场景上下文说明（Worker需要了解任务的定位）
  • 忽略Worker的问题（需先解答再让其继续）
  • 在规范合规性审查未通过时接受“差不多”的结果（规范审查发现问题即表示任务未完成）
  • 跳过审查循环（审查发现问题→实现worker修复→重新审查）
  • 用实现worker的自我审查替代正式审查（两者都必不可少）
  • 在规范合规性审查未通过✅前就开始代码质量审查（顺序错误）
  • 任一审查存在未解决问题时就推进到下一个任务
如果Worker提出问题：
  • 清晰、完整地解答
  • 必要时提供额外上下文
  • 不要催促其开始实现
如果审查发现问题：
  • 由同一实现Worker修复问题
  • 审查人员重新审查
  • 重复此过程直到通过审查
  • 不要跳过重新审查步骤
如果Worker任务失败：
  • 将修复任务分配给专属worker，并提供明确指令
  • 不要手动修复（会导致上下文污染）

Integration

集成要求

Required workflow skills:
  • superpowers:writing-plans - Creates the plan this skill executes
  • superpowers:requesting-code-review - Code review template for reviewer workers
  • superpowers:finishing-a-development-branch - Complete development after all tasks
Workers should use:
  • superpowers:test-driven-development - Workers follow TDD for each task
Alternative workflow:
  • superpowers:executing-plans - Use for parallel session instead of same-session execution
After completing each review stage, follow handbook 
15.04
to create 
tk
tickets for all surfaced issues.
必备工作流技能：
  • superpowers:writing-plans - 生成本技能所需执行的计划
  • superpowers:requesting-code-review - 为审查worker提供代码审查模板
  • superpowers:finishing-a-development-branch - 完成开发分支的收尾工作
Worker应使用的技能：
  • superpowers:test-driven-development - Worker为每个任务遵循测试驱动开发流程
替代工作流：
  • superpowers:executing-plans - 适用于并行会话而非同一会话的执行场景
完成每个审查阶段后，需按照手册
15.04
为所有发现的问题创建
tk
工单。