orchestrate-delivery

Orchestrate Delivery

Run the delivery pipeline as three separated roles so that no context ever grades its own work. The frozen behavior contract is the only interface between them.

Roles

1. Root orchestrator — the session reading this skill, on the strongest available model (Claude Code: Fable). It owns gate checks, contract imports, worktree merges, evidence recording for integration-level proof, and the ship conversation. It does not implement work units and never records review passes for changes it authored.
2. Implementation workers — one subagent per work unit on a Sonnet-class model, each in its own git worktree (Claude Code: spawn the impl-worker agent with isolation: "worktree"). A worker receives the issue ID, its one work unit, the enforced behaviors it owns, and the proof plan. It implements, tests, and reports; it must not edit behavior children, planning state, or review state.
3. Independent reviewer — the Codex CLI, a different vendor and model family, invoked non-interactively with the Loopbreaker MCP server injected. It runs review-planning before implementation and review-invariants after, and it records its own passes, findings, and evidence directly over MCP. Follow references/codex-review.md exactly for the pinned invocation; do not improvise flags.

Protocol

1. Bind. loopbreaker link ISSUE before anything else, in the root and in every worker worktree. The admission hook is keyed to that binding; an unlinked session fails open and every gate below is decorative.
2. Gate. Call delivery_readiness. Drive discovery-interview first when the issue has no approved discovery record, then shape-strategy, plan-feature, and an independent review-planning (via the reviewer role) until implementation.admitted is true. Never start workers before admission.
3. Fan out. Spawn one worker per work unit in parallel. Give each the frozen contract excerpt it owns, verbatim. Workers changing scope report back for a contract decision; they do not resolve it locally.
4. Integrate. Merge worktrees and run the repository verification. Each behavior is verified by loopbreaker prove, whose verdict comes from its registered harness's exit code — the orchestrator records no verdicts of its own. Workers own writing, registering and binding their behaviors' harnesses, and must prove them RED before implementing.
5. Review. Invoke the reviewer for pass 1. Repair findings by re-dispatching the owning worker with the finding's smallest fix, then invoke the reviewer for pass 2, and pass 3 as decision only. Three passes bound both review stages; there is no pass 4.
6. Ship. Read review_ship_status and copy its disposition literally. Review completion never implies shipping readiness. A human authorizes any waiver.