mcpField
T
team-issue

team-issue

github.com/catlog22开发2.1k67 次安装19 周前更新
代码仓库

关于 team-issue

team-issue 是用于协调 issue 解决流程的开发技能,面向需要从分析推进到实现的团队。它支持 Quick、Full 和 Batch 流程,可选审查并包含修复循环。

主要功能

  1. 01协调 issue 解决流程
  2. 02探索上下文并制定方案
  3. 03可选方案审查
  4. 04将任务编组成执行队列
  5. 05支持 Quick、Full 和 Batch 流程
  6. 06审查与修复循环

适用场景

  1. 01从问题探索推进到实现
  2. 02批量处理多个 issue
  3. 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.md
roles/coordinator/commands/
analyze.md
dispatch.md
monitor.md
roles/explorer/
role.md
roles/implementer/
role.md
roles/integrator/
role.md
roles/planner/
role.md
roles/reviewer/
role.md
specs/
pipelines.md
team-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.mdEXPLORE-*false
规划者roles/planner/role.mdSOLVE-*false
审查者roles/reviewer/role.mdAUDIT-*false
集成者roles/integrator/role.mdMARSHAL-*false
实施者roles/implementer/role.mdBUILD-*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

规格参考

错误处理

场景处理方式
未知命令显示可用命令列表并报错
未找到角色显示角色注册表并报错
CLI 工具失败Worker 回退到直接实施
快速推进冲突协调员在下次回调时协调处理
完成操作失败默认保持活动状态
审查拒绝超过 2 轮强制收敛到集成者
给定 ID 未找到问题协调员向用户报告错误
延后处理的 BUILD 数量未知延后到 MARSHAL 回调时处理

评论

支持 Markdown