关于 team-issue
team-issue 是用于协调 issue 解决流程的开发技能,面向需要从分析推进到实现的团队。它支持 Quick、Full 和 Batch 流程,可选审查并包含修复循环。
主要功能
- 01协调 issue 解决流程
- 02探索上下文并制定方案
- 03可选方案审查
- 04将任务编组成执行队列
- 05支持 Quick、Full 和 Batch 流程
- 06审查与修复循环
适用场景
- 01从问题探索推进到实现
- 02批量处理多个 issue
- 03在实施前审查解决方案
MCP 相关
通过 `mcp__ccw-tools__team_msg` 消息总线协调团队工作者,并借助 CLI 工具执行分析与修改。
安装
复制下面的命令,在终端中运行。
$
npx skills add https:/ / github.com/ catlog22/ claude-code-workflow --skill team-issue安装后在 Claude Code 中输入/team-issue确认已加载。
包含的文件
除 SKILL.md 外,安装时一起下载的参考资料和脚本。
roles/coordinator/role.mdroles/coordinator/commands/analyze.mddispatch.mdmonitor.mdroles/explorer/role.mdroles/implementer/role.mdroles/integrator/role.mdroles/planner/role.mdroles/reviewer/role.mdspecs/pipelines.mdteam-config.json详细介绍
团队问题解决
编排问题解决流程:探索上下文 -> 制定解决方案 -> 审查(可选)-> 整理队列 -> 实施。支持 Quick、Full 和 Batch 流程,并包含审查-修复循环。
架构
Skill(skill="team-issue", args="<issue-ids> [--mode=<mode>]")
|
SKILL.md (this file) = Router
|
+--------------+--------------+
| |
no --role flag --role <name>
| |
Coordinator Worker
roles/coordinator/role.md roles/<name>/role.md
|
+-- clarify -> dispatch -> spawn workers -> STOP
|
+-------+-------+-------+-------+
v v v v v
[explor] [plann] [review] [integ] [imple]
角色注册表
| 角色 | 路径 | 前缀 | 内循环 |
|---|---|---|---|
| 协调员 | roles/coordinator/role.md | — | — |
| 探索者 | roles/explorer/role.md | EXPLORE-* | false |
| 规划者 | roles/planner/role.md | SOLVE-* | false |
| 审查者 | roles/reviewer/role.md | AUDIT-* | false |
| 集成者 | roles/integrator/role.md | MARSHAL-* | false |
| 实施者 | roles/implementer/role.md | BUILD-* | false |
角色路由器
解析 $ARGUMENTS:
- 包含
--role <name>→ 读取roles/<name>/role.md,执行阶段 2-4 - 不包含
--role→@roles/coordinator/role.md,执行入口路由器
共享常量
- 会话前缀:
TISL - 会话路径:
.workflow/.team/TISL-<slug>-<date>/ - 团队名称:
issue - CLI 工具:
ccw cli --mode analysis(只读)、ccw cli --mode write(修改) - 消息总线:
mcp__ccw-tools__team_msg(session_id=<session-id>, ...)
Worker 启动模板
协调员使用此模板启动 Worker:
Agent({
subagent_type: "team-worker",
description: "Spawn <role> worker",
team_name: "issue",
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: issue
requirement: <task-description>
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) -> role Phase 2-4 -> built-in Phase 5 (report).`
})
并行启动(Batch 模式,N 个探索者或 M 个实施者实例):
Agent({
subagent_type: "team-worker",
name: "<role>-<N>",
team_name: "issue",
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: issue
requirement: <task-description>
agent_name: <role>-<N>
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=<role>-<N>) -> role Phase 2-4 -> built-in Phase 5 (report).`
})
用户命令
| 命令 | 操作 |
|---|---|
check / status | 查看执行状态图,不推进流程 |
resume / continue | 检查 Worker 状态,推进到下一步 |
会话目录
.workflow/.team/TISL-<slug>-<date>/
├── session.json # Session metadata + pipeline + fix_cycles
├── task-analysis.json # Coordinator analyze output
├── .msg/
│ ├── messages.jsonl # Message bus log
│ └── meta.json # Session state + cross-role state
├── wisdom/ # Cross-task knowledge
│ ├── learnings.md
│ ├── decisions.md
│ ├── conventions.md
│ └── issues.md
├── explorations/ # Explorer output
│ └── context-<issueId>.json
├── solutions/ # Planner output
│ └── solution-<issueId>.json
├── audits/ # Reviewer output
│ └── audit-report.json
├── queue/ # Integrator output (also .workflow/issues/queue/)
└── builds/ # Implementer output
规格参考
- specs/pipelines.md — 流程定义和任务注册表
错误处理
| 场景 | 处理方式 |
|---|---|
| 未知命令 | 显示可用命令列表并报错 |
| 未找到角色 | 显示角色注册表并报错 |
| CLI 工具失败 | Worker 回退到直接实施 |
| 快速推进冲突 | 协调员在下次回调时协调处理 |
| 完成操作失败 | 默认保持活动状态 |
| 审查拒绝超过 2 轮 | 强制收敛到集成者 |
| 给定 ID 未找到问题 | 协调员向用户报告错误 |
| 延后处理的 BUILD 数量未知 | 延后到 MARSHAL 回调时处理 |
评论
支持 Markdown