autopilot

# Autopilot: hands-off plan→ship pipeline that chains existing skills `autopilot` runs a build request from plan to shipped without re-prompting at every step. It is a **chain**: each phase invokes an existing ODIN skill via the Skill tool and gates on the result before the next phase begins. It owns sequencing, the phase gates, and the terminal report; nothing else. It writes no code surface of its own; the chained skills do. ## When to Apply - The user hands an execution-ready task and wants it taken from plan to shipped without step-by-step approval: "autopilot", "ship it end to end", "take it from plan to PR". - A concrete change is specified, enough for the approved plan to name implementation units. The pipeline executes; it does not discover what to build. ## When NOT to Apply - **A single execution step against an approved plan** → `work`. autopilot wraps `work` with the rest of the arc; if that arc is unwanted, call `work` directly. ## Inputs and Flags - `[task]`: the execution-ready request the approved plan covers. Required; an empty or ambiguous task fails the precondition below — the chain does not start. - `against <ref>`: base-ref override forwarded to the diff-scoped phases (`simplify`, `review`). - `mode:local`: force local-only (skip push + CI) even when a remote exists. - `mode:headless`: non-interactive overlay; pass through to each chained skill's headless variant where it has one. No phase prompts the user; a gate that would prompt instead HALTs w...