orchestratelisted
Install: claude install-skill matthull/my-skills
# Orchestration
Coordinate work through subagents and teams. The orchestrator's job is to stay thin, delegate effectively, and steer when needed — never to do the work itself.
**Input:** `{{input}}`
---
## On Skill Load — Route to Planning or Execution
**The operator invoked `/orchestrate`. Before doing anything, determine whether a plan already exists.**
Immediately on skill load:
1. **Resolve `<task-dir>`** from operator input, inference, or defaults (see Task Dir Resolution below)
2. **Check if `<task-dir>/task-plan.md` exists**
- **If YES → skip to Execution.** The plan was already approved. Do NOT enter Plan Mode. Go directly to the "Execution (Post-Plan Mode)" section below. The plan is the durable state — resumption reads it and picks up from the last completed phase.
- **If NO → enter Plan Mode** and build the plan (continue with step 3 below)
3. **Enter Plan Mode** using the EnterPlanMode tool
4. **Check for existing triage output** (see Step 0 below) — this determines whether Pass 1 is needed
5. **Create tasks** using TaskCreate:
- If no triage exists: Task A: "Triage — scope goal + completion criteria" (start `in_progress`), Task B: "Build and approve task plan" (leave `pending`)
- If triage exists and is fresh: Task B only: "Build and approve task plan" (start `in_progress`)
6. Execute **Step 0: Triage** (below)
7. Once the operator approves the plan, **write a durable copy** to `<task-dir>/task-plan.md` using the Write tool. The Plan Mode plan