orchestrate

Orchestrate

The root skill. The human binds intent here; this skill composes leaf skills to fulfill it. It holds the only warm context. Leaf skills run as fresh, isolated dispatches and keep none.

Core principle: Organize by capability, not by role. The human sets direction at the start and accepts the result at the end. In between, the run is lights-out: objective verify gates each step, not a human.

This skill is the designated root. It does not orchestrate itself. There is no step above intent.

The loop

1. Bind intent. Read the human's goal and constraints. This is the only place intent enters. Then run the first-run preflight (below) before any wiring.
2. Select. Read the skill registry (the description: line of every SKILL.md in the runtime's skills directory). Pick skills by that when-to-use description. Load a skill's full contract only when it is a candidate — never load every contract at once.
3. Wire (emergent, not hardcoded). Build the path by matching one skill's outputs to the next skill's inputs. Skills do not know each other; only you do. Do not assume a fixed pipeline — wire what this intent needs.
4. Dispatch. Hand the skill exactly the inputs it declares, as files — resolving each logical namespace it reads/writes to a physical path via core-config.yaml (see Namespace resolution). If the runtime supports isolated agents, run each leaf as a fresh dispatch on the model its requires.model tier resolves to (see Model tier). Dispatch independent steps concurrently and await them in the same turn; keep dependent steps sequential. Never fire-and-forget a background agent. If the runtime has no isolated-agent capability, execute leaves sequentially in the current context, reloading only the declared inputs before each step. Isolation is preferred; it is not required for correctness.
5. Verify (gate) — executable, not prose. Prove the skill's verify with a REAL command you run yourself via Bash, and capture the proof: