/team-issue

name: team-issue
disable-model-invocation: true
description: 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".
allowed-tools: TeamCreate(*), TeamDelete(*), SendMessage(*), TaskCreate(*), TaskUpdate(*), TaskList(*), TaskGet(*), Agent(*), AskUserQuestion(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), mcp__maestro__team_msg(*)
session-mode: run

<required_reading> @~/.maestro/workflows/run-mode-lite.md </required_reading>

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](roles/coordinator/role.md) | — | — | | explorer | [roles/explorer/role.md](roles/explorer/role.md) | EXPLORE-* | false | | planner | [roles/planner/role.md](roles/planner/role.md) | SOLVE-* | false | | reviewer | [roles/reviewer/role.md](roles/reviewer/role.md) | AUDIT-* | false | | integrator | [roles/integrator/role.md](roles/integrator/role.md) | MARSHAL-* | false | | implementer | [roles/implementer/role.md](roles/implementer/role.md) | BUILD-* | false |

Pre-load (coordinator, before dispatch)

1. **Codebase docs**: If `.workflow/codebase/ARCHITECTURE.md` exists, read for module boundaries 2. **Specs (coding)**: `maestro load --type spec --category coding` — load coding constraints as shared context 3. **Specs (debug)**: `maestro load --type spec --category debug` — load debug constraints as shared context 4. **Wiki knowledge**: `maestro search "issue resolution fix" --json` — top 5 entries as prior context 5. All optional — proceed without if unavailable

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**: `{run_dir}/work/team/`
• **Team name**: `issue`
• **CLI tools**: `maestro delegate --mode analysis` (read-only), `maestro delegate --mode write` (modifications)
• **Message bus**: `mcp__maestro__team_msg(session_id=<run-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: {run_dir}/work/team
session_id: <run-id>
team_name: issue
requirement: <task-description>
inner_loop: false

## Progress Milestones
session_id: <run-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: {run_dir}/work/team
session_id: <run-id>
team_name: issue
requirement: <task-description>
agent_name: <role>-<N>
inner_loop: false

## Progress Milestones
session_id: <run-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 | |---------|--------| | `check` / `status` | View execution status graph, no advancement | | `resume` / `continue` | Check worker states, advance next step |

Session Directory

{run_dir}/work/team/
├── team-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
├── {run_dir}/outputs/solutions/                      # Planner output
│   └── solution-<issueId>.json
├── {run_dir}/outputs/audits/                         # Reviewer output
│   └── audit-report.json
├── {run_dir}/outputs/queue/                            # Integrator output
└── {run_dir}/outputs/builds/                         # Impleme