team-lifecycle-v4

Team Lifecycle v4

编排多 Agent 软件开发：规范 → 规划 → 实现 → 测试 → 评审。

架构

Skill(skill="team-lifecycle-v4", args="task description")
                    |
         SKILL.md (this file) = Router
                    |
     +--------------+--------------+
     |                             |
  no --role flag              --role <name>
     |                             |
  Coordinator                  Worker
  roles/coordinator/role.md    roles/<name>/role.md
     |
     +-- analyze → dispatch → spawn → STOP
                                 |
                    +--------+---+--------+
                    v        v            v
             [team-worker]  ...    [team-supervisor]
              per-task               resident agent
              lifecycle              message-driven
                                     (woken via SendMessage)

角色注册表

角色	路径	前缀	内循环
coordinator	roles/coordinator/role.md	—	—
analyst	roles/analyst/role.md	RESEARCH-*	false
writer	roles/writer/role.md	DRAFT-*	true
planner	roles/planner/role.md	PLAN-*	true
executor	roles/executor/role.md	IMPL-*	dynamic
tester	roles/tester/role.md	TEST-*	false
reviewer	roles/reviewer/role.md	REVIEW-, QUALITY-, IMPROVE-*	false
supervisor	roles/supervisor/role.md	CHECKPOINT-*	false

角色路由器

解析 $ARGUMENTS：

• 包含 --role <name> → 读取 roles/<name>/role.md，执行阶段 2-4
• 不包含 --role → @roles/coordinator/role.md，执行入口路由器

共享常量

• 会话前缀：TLV4
• 会话路径：.workflow/.team/TLV4-<slug>-<date>/
• CLI 工具：ccw cli --mode analysis（只读），ccw cli --mode write（修改）
• 消息总线：mcp__ccw-tools__team_msg(session_id=<session-id>, ...)

Worker 启动模板

Coordinator 使用此模板启动 Worker：

Agent({
  subagent_type: "team-worker",
  description: "Spawn <role> worker",
  team_name: <team-name>,
  name: "<role>",
  run_in_background: true,
  prompt: `## Role Assignment
role: <role>
role_spec: <skill_root>/roles/<role>/role.md
session: <session-folder>
session_id: <session-id>
team_name: <team-name>
requirement: <task-description>
inner_loop: <true|false>

## Progress Milestones
session_id: <session-id>
Report progress via team_msg at natural phase boundaries (context loaded -> core work done -> verification).
Report blockers immediately via team_msg type="blocker".
Report completion via team_msg type="task_complete" after final SendMessage.

Read role_spec file (@<skill_root>/roles/<role>/role.md) to load Phase 2-4 domain instructions.
Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5 (report).`
})

Supervisor 启动模板

Supervisor 是常驻 Agent（独立于 team-worker）。在会话初始化期间启动一次，每个 CHECKPOINT 任务通过 SendMessage 唤醒。

启动（阶段 2 — 每个会话一次）

Agent({
  subagent_type: "team-supervisor",
  description: "Spawn resident supervisor",
  team_name: <team-name>,
  name: "supervisor",
  run_in_background: true,
  prompt: `## Role Assignment
role: supervisor
role_spec: <skill_root>/roles/supervisor/role.md
session: <session-folder>
session_id: <session-id>
team_name: <team-name>
requirement: <task-description>

## Progress Milestones
session_id: <session-id>
Report progress via team_msg at natural phase boundaries (context loaded -> core work done -> verification).
Report blockers immediately via team_msg type="blocker".
Report completion via team_msg type="task_complete" after final SendMessage.

Read role_spec file (@<skill_root>/roles/supervisor/role.md) to load checkpoint definitions.
Init: load baseline context, report ready, go idle.
Wake cycle: coordinator sends checkpoint requests via SendMessage.`
})

唤醒（handleSpawnNext — 每个 CHECKPOINT 任务）

SendMessage({
  type: "message",
  recipient: "supervisor",
  content: `## Checkpoint Request
task_id: <CHECKPOINT-NNN>
scope: [<upstream-task-ids>]
pipeline_progress: <done>/<total> tasks completed`,
  summary: "Checkpoint request: <CHECKPOINT-NNN>"
})

关闭（handleComplete）

SendMessage({
  type: "shutdown_request",
  recipient: "supervisor",
  content: "Pipeline complete, shutting down supervisor"
})

用户命令

命令	操作
check / status	查看执行状态图
resume / continue	前进到下一步
revise <TASK-ID> [feedback]	修改指定任务
feedback <text>	注入反馈以进行修改
recheck	重新运行质量检查
improve [dimension]	自动改进最薄弱的维度

完成操作

当流水线完成时，Coordinator 会显示：

AskUserQuestion({
  questions: [{
    question: "Pipeline complete. What would you like to do?",
    header: "Completion",
    multiSelect: false,
    options: [
      { label: "Archive & Clean (Recommended)", description: "Archive session, clean up team" },
      { label: "Keep Active", description: "Keep session for follow-up work" },
      { label: "Export Results", description: "Export deliverables to target directory" }
    ]
  }]
})

规范参考

• specs/pipelines.md — 流水线定义和任务注册表
• specs/quality-gates.md — 质量门槛标准和评分
• specs/knowledge-transfer.md — 工件和状态传输协议

会话目录

.workflow/.team/TLV4-<slug>-<date>/
├── team-session.json           # Session state + role registry
├── spec/                       # Spec phase outputs
├── plan/                       # Implementation plan + TASK-*.json
├── artifacts/                  # All deliverables
├── wisdom/                     # Cross-task knowledge
├── explorations/               # Shared explore cache
├── discussions/                # Discuss round records
└── .msg/                       # Team message bus

错误处理

场景	解决方案
未知命令	显示可用命令列表并报错
未找到角色	显示角色注册表并报错
CLI 工具失败	Worker 回退到直接实现
快速推进冲突	Coordinator 在下次回调时协调
Supervisor 崩溃	使用 recovery: true 重新启动，并从现有报告自动重建
Supervisor 尚未准备好处理 CHECKPOINT	启动/重新启动 Supervisor，等待就绪后再唤醒
完成操作失败	默认保持活动状态