team-ultra-analyze

团队 Ultra Analyze

深度协作分析：探索 -> 分析 -> 讨论 -> 综合。支持 Quick/Standard/Deep 流水线模式，深度可配置（N 个并行 Agent）。讨论循环支持用户引导的渐进式理解。

架构

Skill(skill="team-ultra-analyze", args="<topic>")
                    |
         SKILL.md (this file) = Router
                    |
     +--------------+--------------+
     |                             |
  no --role flag              --role <name>
     |                             |
  Coordinator                  Worker
  roles/coordinator/role.md    roles/<name>/role.md
     |
     +-- analyze -> dispatch -> spawn workers -> STOP
                                    |
                    +-------+-------+-------+-------+
                    v       v       v       v
                 [team-worker agents, each loads roles/<role>/role.md]

Pipeline (Standard mode):
  [EXPLORE-1..N](parallel) -> [ANALYZE-1..N](parallel) -> DISCUSS-001 -> SYNTH-001

Pipeline (Deep mode):
  [EXPLORE-1..N] -> [ANALYZE-1..N] -> DISCUSS-001 -> ANALYZE-fix -> DISCUSS-002 -> ... -> SYNTH-001

Pipeline (Quick mode):
  EXPLORE-001 -> ANALYZE-001 -> SYNTH-001

角色注册表

角色	路径	前缀	内部循环
coordinator	roles/coordinator/role.md	—	—
explorer	roles/explorer/role.md	EXPLORE-*	false
analyst	roles/analyst/role.md	ANALYZE-*	false
discussant	roles/discussant/role.md	DISCUSS-*	false
synthesizer	roles/synthesizer/role.md	SYNTH-*	false

角色路由器

解析 $ARGUMENTS：

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

共享常量

• 会话前缀：UAN
• 会话路径：.workflow/.team/UAN-<slug>-<date>/
• 团队名称：ultra-analyze
• 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: "ultra-analyze",
  name: "<agent-name>",
  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: ultra-analyze
requirement: <topic-description>
agent_name: <agent-name>
inner_loop: 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, owner=<agent-name>) -> role Phase 2-4 -> built-in Phase 5 (report).`
})

用户命令

命令	操作
check / status	输出执行状态图，不推进流水线
resume / continue	检查 Worker 状态，推进到下一流水线步骤

会话目录

.workflow/.team/UAN-{slug}-{YYYY-MM-DD}/
+-- .msg/messages.jsonl          # Message bus log
+-- .msg/meta.json               # Session metadata + cross-role state
+-- discussion.md                # Understanding evolution and discussion timeline
+-- explorations/                # Explorer output
|   +-- exploration-001.json
|   +-- exploration-002.json
+-- analyses/                    # Analyst output
|   +-- analysis-001.json
|   +-- analysis-002.json
+-- discussions/                 # Discussant output
|   +-- discussion-round-001.json
+-- conclusions.json             # Synthesizer output
+-- wisdom/                      # Cross-task knowledge
|   +-- learnings.md
|   +-- decisions.md
|   +-- conventions.md
|   +-- issues.md

完成操作

流水线完成后，Coordinator 会提供：

AskUserQuestion({
  questions: [{
    question: "Ultra-Analyze 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" }
    ]
  }]
})

选项	操作
归档并清理	将会话状态更新为 "completed" -> TeamDelete() -> 输出最终摘要
保持活动	将会话状态更新为 "paused" -> 输出恢复说明
导出结果	通过 AskUserQuestion 询问目标路径 -> 复制交付成果 -> 归档并清理

规范参考

• specs/team-config.json — 团队配置和流水线设置

错误处理

情况	解决方案
未知的 --role 值	显示角色注册表列表并报错
未找到角色文件	显示预期路径（roles/{name}/role.md）并报错
讨论循环超过 5 轮仍陷入停滞	强制进行综合，并提供继续选项
CLI 工具不可用	回退链：gemini -> codex -> 手动分析
Explorer Agent 失败	使用可用上下文继续，并注明限制
快速推进冲突	Coordinator 在下一次回调时协调解决
完成操作失败	默认选择“保持活动”