team-perf-opt

团队性能优化

分析应用性能，识别瓶颈，设计优化策略，实施变更，基准测试改进效果，并审查代码质量。

架构

Skill(skill="team-perf-opt", 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 workers -> STOP
                                    |
                    +-------+-------+-------+-------+-------+
                    v       v       v       v       v
                 [profiler] [strategist] [optimizer] [benchmarker] [reviewer]
                 (team-worker agents)

Pipeline (Single mode):
  PROFILE-001 -> STRATEGY-001 -> IMPL-001 -> BENCH-001 + REVIEW-001 (fix cycle)

Pipeline (Fan-out mode):
  PROFILE-001 -> STRATEGY-001 -> [IMPL-B01..N](parallel) -> BENCH+REVIEW per branch

Pipeline (Independent mode):
  [Pipeline A: PROFILE-A->STRATEGY-A->IMPL-A->BENCH-A+REVIEW-A]
  [Pipeline B: PROFILE-B->STRATEGY-B->IMPL-B->BENCH-B+REVIEW-B] (parallel)

角色注册表

角色	路径	前缀	内循环
coordinator	roles/coordinator/role.md	—	—
profiler	roles/profiler/role.md	PROFILE-*	false
strategist	roles/strategist/role.md	STRATEGY-*	false
optimizer	roles/optimizer/role.md	IMPL-, FIX-	true
benchmarker	roles/benchmarker/role.md	BENCH-*	false
reviewer	roles/reviewer/role.md	REVIEW-, QUALITY-	false

角色路由器

解析 $ARGUMENTS：

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

共享常量

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

工作线程启动模板

Coordinator 使用此模板启动工作线程：

Agent({
  subagent_type: "team-worker",
  description: "Spawn <role> worker",
  team_name: "perf-opt",
  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: perf-opt
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).`
})

内循环角色（optimizer）：动态设置 inner_loop — 单任务模式下设为 true，扇出/独立（并行分支）模式下设为 false。 单任务角色（profiler、strategist、benchmarker、reviewer）：设置 inner_loop: false。

用户命令

命令	操作
check / status	输出执行状态图（按分支分组），不推进流程
resume / continue	检查工作线程状态，推进到下一步
revise <TASK-ID> [feedback]	创建修订任务并级联下游（限定在分支内）
feedback <text>	分析反馈影响，创建有针对性的修订链
recheck	重新运行质量检查
improve [dimension]	自动改进最薄弱的维度

会话目录

.workflow/.team/PERF-OPT-<slug>-<date>/
+-- session.json                    # Session metadata + status + parallel_mode
+-- artifacts/
|   +-- baseline-metrics.json       # Profiler: before-optimization metrics
|   +-- bottleneck-report.md        # Profiler: ranked bottleneck findings
|   +-- optimization-plan.md        # Strategist: prioritized optimization plan
|   +-- benchmark-results.json      # Benchmarker: after-optimization metrics
|   +-- review-report.md            # Reviewer: code review findings
|   +-- branches/B01/...            # Fan-out branch artifacts
|   +-- pipelines/A/...             # Independent pipeline artifacts
+-- explorations/                   # Shared explore cache
+-- wisdom/patterns.md              # Discovered patterns and conventions
+-- discussions/                    # Discussion records
+-- .msg/messages.jsonl             # Team message bus
+-- .msg/meta.json                  # Session metadata

完成操作

当流水线完成时：

AskUserQuestion({
  questions: [{
    question: "Team 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 — 流水线定义和任务注册表
• specs/team-config.json — 团队配置

错误处理

场景	解决方案
未知的 --role 值	报错并列出角色注册表
未找到角色文件	报错并显示预期路径（roles/{name}/role.md）
性能分析工具不可用	回退到静态分析方法
检测到基准测试性能回退	自动创建包含回退详情的 FIX 任务
审查—修复周期超过 3 次迭代	升级给用户处理
一个分支的 IMPL 失败	将该分支标记为失败，其他分支继续
快速推进冲突	Coordinator 在下次回调时协调解决
完成操作失败	默认设为保持活动状态