express-orchestratorlisted

# Express Orchestrator — Stateless Sub-Agent Flow Run a small change end-to-end through dedicated sub-agents while keeping every working artifact in the orchestrator's own context. Create no files of any kind beyond the repo code, tests, and docs the change itself requires — no state files, no worklogs, no plans on disk, no notes, no logs. The only output of the flow is the changed code. Invocation: `/express-orchestrator <task description>`. No resume: if the session is lost mid-flight, inspect the current state of the touched files and restart from there. ## Scope Guard — Check First, Re-check Mid-flight Express fits only when ALL of these hold: - Expected change: **≤ 5 files** and **≤ ~200 lines**. - Behavior described in the project's specs (if it keeps any) does not change materially. - The root cause is already known or findable in **one research pass**. - The user does not want a persistent planning record. If any condition breaks — at assessment or at any later point — STOP, tell the user the task exceeds Express scope, and ask how to proceed: split it into smaller Express-sized pieces, continue anyway at their explicit request, or handle it outside this skill. Never silently continue an oversized task. If work is already in progress, follow the Abort Protocol. ## Path Selection: Standard vs Micro Classify at step 1 and state the choice at plan confirmation: - **Standard** — the default flow below. - **Micro** — expected change ≤ ~10 lines in 1 file AND the