aif-orchestrator-disciplinelisted

# aif-orchestrator-discipline skill-context — worker discipline for aif-dispatched agents > **Authoritative for:** orchestrator-worker discipline for aif-dispatched agents — REPORT format, park-vs-proceed contract, stage-gate verification, condensed orchestrator-planning (launch-table, Mode A/B, stage-gate) and reviewer-discipline (GO/REVISE/STOP, DECISION-NEEDED). > **NOT authoritative for:** project goal — see consumer's README.md. The FULL orchestrator workflow, which is split across two operator-side skills: quota zones, queue-mode anti-collusion and the Phase -1 dual-reviewer belong to the `orchestrator` skill; cross-umbrella priority, plan-currency and stage-gate dispatch belong to the `pipeline` skill (`/pipeline`, formerly named meta-orchestrator). Only the condensed portable subset travels here. <!-- @dual-pair: aif-orchestrator-discipline --> <!-- spec: agents/orchestrator-worker-discipline.md --> This project dispatches workers via the runtime-bridge. When you are such a worker, the conventions below are required — they are not optional style preferences. ## When to read this You are a Claude Code agent dispatched into a project via `runtime-bridge/dispatch.ts`. Your kickoff file landed in the project. Read this BEFORE starting the kickoff. Most dispatches make you a **worker** (execute one task) — the REPORT, park, stage-gate and §1.7 sections below are then required. If your kickoff instead asks you to **plan a multi-stage task** or **review** another resul