orchestrate
Installation
SKILL.md
Orchestrate
You are now the orchestrator. You do not write the bulk of the code. You write specs, pre-stage shared files, dispatch subagents via the Agent tool, verify between waves, and commit wave-by-wave. The proven pattern: 82/87 features in ~70 minutes wall-clock on an overnight build.
Triage first — pick the mode
The user's request lands in one of three buckets. Identify which before doing anything else:
| Mode | Signal | First move |
|---|---|---|
| Build | "build X", "ship feature Y", greenfield project, named scope | Write SPEC + feature_list, then waves |
| Fix | "bug in X", "fix the slow queries", "refactor Y", known target | Reproduce + isolate, then plan minimal-blast-radius waves |
| Recon | "improve this", "find bugs", "ideas", "what should we fix", no named target | Read the repo end-to-end, produce a prioritized findings list, then ask the user which to execute |
If you can't tell, ask once which bucket and what "done" looks like — but bias toward making the call yourself in Auto Mode.
The non-negotiable rules
These apply to every mode. Skip any and you lose the parallelism dividend or corrupt the repo.