orchestrate
orchestrate
Read the tracker, and work the ready-for-agent tickets it holds on the branch the developer is already on: a wave at a time, each ticket built by its own subagent, verified by a second one that did not build it, and integrated into that branch as its wave completes.
Run uv run "$HERE/scripts/invoke.py" — $HERE is the directory that holds this SKILL.md — with everything the user typed after /orchestrate, verbatim and however many lines, on stdin. Exit 0: do what it prints. On any other exit, if you introduced a known construction error and can correct it while preserving the user's request and authority, account for effects already produced, submit the corrected invocation through the same shim, and continue from the failed boundary; a refusal before the operation starts consumes no operation. Otherwise show what it printed to the user verbatim and stop. Never repair input the user supplied, or automatically retry exact help, an unmet dependency, an unrelated failure, or a failure whose origin or valid correction is unknown.
Arguments
A run may be aimed at as many tickets and specs as the user cares to name, one operand each; reconciliation names exactly one ticket. --model locks only the building model and --deliberation locks only the building deliberation; neither reaches a verdict. --fast is the run's third lock, held for the whole run like the other two rather than for one wave of it; it counts finishing the work in elapsed time rather than in money, which is what somebody waiting on the run is actually spending. Without it the run is ordered on the developer's standing choice between time and cost, set with /model-selector objective, and on money where none is set, and the engine holds whichever its first route was answered on for the rest of the run. --max-deliberation is the building roles' deliberation ceiling: model-selector still chooses the level and chooses none above the deliberation ceiling, xhigh applying where the developer names none. It is held for the whole run beside the three locks without being one; like them it never reaches a verdict, and unlike --model and --deliberation it is not part of the approval identity. --approval binds only the first plan of this invocation to the identity the caller supplied. --state-dir is yours to pass rather than the developer's to type, and step 1 says where it comes from.
Park and Resume Rule
The amendment budget is per-ticket-lifetime, not per run cycle: tracker markers are append-only evidence, so parking changes neither amends_spent nor the remaining budget. Step 3 and step 6 report every parked ticket with the amends_spent value in its plan entry. A caller can therefore subtract that value from the limit of two to know exactly how many further amendments remain.
On re-entry, step 4 sends a ticket with a recorded amend_state to step 9. Step 5 also sends a ticket with a recorded amend_state to step 9 after isolation. Step 6 sends a ticket with a recorded amend_state to step 9 instead of dispatching an initial builder; the initial-build brief is never dispatched for recorded amendment work. Prior verdicts remain ticket evidence, and step 9 supplies the persisted immediately preceding verdict verbatim to the resumed builder.
The preserved commits are its mandatory base. On a resumed isolated ticket, step 5 requires isolate to bring the run branch forward into the preserved ticket branch before any builder is dispatched. Exit 0 continues from that tree. Exit 1 for uncommitted work leaves the ticket parked and reports that it is waiting for a hand. Exit 2 carries collisions and collided_with and routes repair-<number>: the collision-repair brief says the ticket is being resumed, merges the run branch into the ticket branch, and is not verified or integrated by itself. A repairer's unresolved disagreement parks the ticket without recording an outcome or spending an amendment; otherwise the repaired tree goes directly to the resumed step 9 amend, whose fresh full-ticket verifier judges the whole result.
A ticket parked during its initial build, with no recorded amend_state, resumes through step 6 from the preserved commits. Its ordinary initial brief is prefixed with one sentence stating that those commits are the base and are not rewritten.