team-roadmap-dev

团队路线图开发

以路线图为驱动的开发，采用分阶段执行流水线。协调器与用户讨论路线图并管理阶段转换。工作者以 team-worker Agent 的身份启动。

架构

Skill(skill="team-roadmap-dev", args="<task-description>")
                    |
         SKILL.md (this file) = Router
                    |
     +--------------+--------------+
     |                             |
  no --role flag              --role <name>
     |                             |
  Coordinator                  Worker
  roles/coordinator/role.md    roles/<name>/role.md
     |
     +-- roadmap-discuss -> dispatch -> spawn workers -> STOP
                                    |
                    +-------+-------+-------+
                    v       v       v
                 [planner] [executor] [verifier]
                 (team-worker agents)

Pipeline (per phase):
  PLAN-N01 -> EXEC-N01 -> VERIFY-N01 (gap closure loop if needed)

Multi-phase:
  Phase 1 -> Phase 2 -> ... -> Phase N -> Complete

角色注册表

角色	路径	前缀	内循环
协调器	roles/coordinator/role.md	—	—
规划器	roles/planner/role.md	PLAN-*	true
执行器	roles/executor/role.md	EXEC-*	true
验证器	roles/verifier/role.md	VERIFY-*	true

角色路由器

解析 $ARGUMENTS：

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

共享常量

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

工作者启动模板

协调器使用此模板启动工作者：

Agent({
  subagent_type: "team-worker",
  description: "Spawn <role> worker",
  team_name: "roadmap-dev",
  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: roadmap-dev
requirement: <task-description>
inner_loop: true

## 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).`
})

所有工作者角色（规划器、执行器、验证器）：设置 inner_loop: true。

用户命令

命令	操作
check / status	输出执行状态图（按阶段分组），不推进流程
resume / continue	检查工作者状态，推进到下一步

会话目录

.workflow/.team/RD-<slug>-<date>/
+-- roadmap.md                 # Phase plan with requirements and success criteria
+-- state.md                   # Living memory (<100 lines)
+-- config.json                # Session settings (mode, depth, gates)
+-- wisdom/                    # Cross-task knowledge accumulation
|   +-- learnings.md
|   +-- decisions.md
|   +-- conventions.md
|   +-- issues.md
+-- phase-1/                   # Per-phase artifacts
|   +-- context.md
|   +-- IMPL_PLAN.md
|   +-- TODO_LIST.md
|   +-- .task/IMPL-*.json
|   +-- summary-*.md
|   +-- verification.md
+-- phase-N/
|   +-- ...
+-- .msg/
    +-- messages.jsonl          # Team message bus log
    +-- meta.json               # Session metadata + shared state

完成操作

流水线完成时：

AskUserQuestion({
  questions: [{
    question: "Roadmap Dev pipeline complete. What would you like to do?",
    header: "Completion",
    multiSelect: false,
    options: [
      { label: "Archive & Clean (Recommended)", description: "Archive session, clean up tasks and team resources" },
      { label: "Keep Active", description: "Keep session active for follow-up work or inspection" },
      { label: "Export Results", description: "Export deliverables to a specified location, then clean" }
    ]
  }]
})

规范参考

• specs/pipelines.md — 流水线定义和任务注册表

错误处理

场景	解决方法
未知的 --role 值	显示角色注册表列表并报错
找不到角色文件	显示预期路径（roles/{name}/role.md）并报错
缺少 project-tech.json	协调器调用 /workflow:spec:setup
阶段验证存在缺漏	协调器启动缺漏闭环（最多 3 轮）
达到缺漏闭环最大轮数（3 轮）	向用户报告并请求指引
工作者崩溃	重新启动工作者并重新分配任务
会话损坏	尝试恢复；若失败则手动协调