orchestrate
Installation
SKILL.md
Orchestrate — root decides, specialists contribute
The model running the current task is always the root orchestrator. It owns intent, architecture, the canonical plan, packet boundaries, integration, acceptance commands, and the final answer. Planner and Advisor are read-only contributors. Executors implement bounded packets. No child result is accepted without root verification.
State on disk
.orchestrate/ # gitignored, survives tasks
SPRINT.md # status board; first file read on resume
HANDOFF.md # compact cross-task context named by SPRINT.md
plans/NNN-<slug>.md # canonical plan + Advisor findings ledger
packets/NNN-<slug>.md # one independently verifiable implementation slice