mcpField
T
team-issue

team-issue

github.com/catlog22Development2.1k67 installsUpdated 19w ago
Repository

About team-issue

team-issue coordinates an issue-resolution workflow for development teams, from context exploration through implementation. It offers Quick, Full, and Batch pipelines, with optional review and a review-fix cycle.

Key features

  1. 01Coordinate issue resolution
  2. 02Explore context and plan solutions
  3. 03Optional solution review
  4. 04Marshal tasks into an execution queue
  5. 05Quick, Full, and Batch pipelines
  6. 06Review-fix cycle

Use cases

  1. 01Move from issue exploration to implementation
  2. 02Process multiple issues in a batch
  3. 03Review a proposed solution before implementation

MCP support

It coordinates workers through the `mcp__ccw-tools__team_msg` message bus and uses CLI tools for analysis and modifications.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/catlog22/claude-code-workflow --skill team-issue

After installing, type/team-issuein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with 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

Details

From the project README

Team Issue Resolution

Orchestrate issue resolution pipeline: explore context -> plan solution -> review (optional) -> marshal queue -> implement. Supports Quick, Full, and Batch pipelines with review-fix cycle.

Architecture

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]

Role Registry

RolePathPrefixInner Loop
coordinatorroles/coordinator/role.md——
explorerroles/explorer/role.mdEXPLORE-*false
plannerroles/planner/role.mdSOLVE-*false
reviewerroles/reviewer/role.mdAUDIT-*false
integratorroles/integrator/role.mdMARSHAL-*false
implementerroles/implementer/role.mdBUILD-*false

Role Router

Parse $ARGUMENTS:

  • Has --role <name> → Read roles/<name>/role.md, execute Phase 2-4
  • No --role → @roles/coordinator/role.md, execute entry router

Shared Constants

  • Session prefix: TISL
  • Session path: .workflow/.team/TISL-<slug>-<date>/
  • Team name: issue
  • CLI tools: ccw cli --mode analysis (read-only), ccw cli --mode write (modifications)
  • Message bus: mcp__ccw-tools__team_msg(session_id=<session-id>, ...)

Worker Spawn Template

Coordinator spawns workers using this template:

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

Parallel spawn (Batch mode, N explorer or M implementer instances):

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

User Commands

CommandAction
check / statusView execution status graph, no advancement
resume / continueCheck worker states, advance next step

Session Directory

.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 Reference

Error Handling

ScenarioResolution
Unknown commandError with available command list
Role not foundError with role registry
CLI tool failsWorker fallback to direct implementation
Fast-advance conflictCoordinator reconciles on next callback
Completion action failsDefault to Keep Active
Review rejection exceeds 2 roundsForce convergence to integrator
No issues found for given IDsCoordinator reports error to user
Deferred BUILD count unknownDefer to MARSHAL callback

Comments

Markdown supported