Claude-Code-Workflow team-issue
Unified team skill for issue resolution. Uses team-worker agent architecture with role directories for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on "team issue".
install
source · Clone the upstream repo
git clone https://github.com/catlog22/Claude-Code-Workflow
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/catlog22/Claude-Code-Workflow "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/team-issue" ~/.claude/skills/catlog22-claude-code-workflow-team-issue && rm -rf "$T"
manifest:
.claude/skills/team-issue/SKILL.mdsource content
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
| Role | Path | Prefix | Inner Loop |
|---|---|---|---|
| coordinator | roles/coordinator/role.md | — | — |
| explorer | roles/explorer/role.md | EXPLORE-* | false |
| planner | roles/planner/role.md | SOLVE-* | false |
| reviewer | roles/reviewer/role.md | AUDIT-* | false |
| integrator | roles/integrator/role.md | MARSHAL-* | false |
| implementer | roles/implementer/role.md | BUILD-* | false |
Role Router
Parse
$ARGUMENTS:
- Has
→ Read--role <name>
, execute Phase 2-4roles/<name>/role.md - No
→--role
, execute entry router@roles/coordinator/role.md
Shared Constants
- Session prefix:
TISL - Session path:
.workflow/.team/TISL-<slug>-<date>/ - Team name:
issue - CLI tools:
(read-only),ccw cli --mode analysis
(modifications)ccw cli --mode write - 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
| Command | Action |
|---|---|
/ | View execution status graph, no advancement |
/ | Check 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
- specs/pipelines.md — Pipeline definitions and task registry
Error Handling
| Scenario | Resolution |
|---|---|
| Unknown command | Error with available command list |
| Role not found | Error with role registry |
| CLI tool fails | Worker fallback to direct implementation |
| Fast-advance conflict | Coordinator reconciles on next callback |
| Completion action fails | Default to Keep Active |
| Review rejection exceeds 2 rounds | Force convergence to integrator |
| No issues found for given IDs | Coordinator reports error to user |
| Deferred BUILD count unknown | Defer to MARSHAL callback |