autopilot

# autopilot — the whole loop, one yes `/autopilot <task>` — run the full pipeline, stop at an open PR `/autopilot <task> --merge` — also merge, once every gate is green `/autopilot resume <change>` — pick up a crashed, aborted, or parked run `/autopilot status` — report runs in flight under `out/dev/` Answer one question: **what would come back if this task were handed to a careful team and nobody watched over their shoulder?** The other coding skills put a human at every gate; this one replaces those gates with the things that made them work — fresh-context review, diverse critique, and a test suite as the arbiter — and reserves the human for exceptions. Human *on* the loop, not *in* it: you sign once, you get a PR, and anything the pipeline couldn't settle honestly comes back **parked**, not guessed. ## The charter — one yes, spelled out The invocation is the consent. Echo this before running, then don't ask again: - **WILL:** read anything in the repo; write state under `out/dev/<slug>/`; create GitHub issues labeled `autopilot`; create and push branches `autopilot/<slug>/*`; open **one** PR; comment on and close its own issues; with `--merge`, merge that PR once every gate is green. - **NEVER:** push to the default branch directly, force-push, rewrite history, delete branches or issues it didn't create, weaken a test to get green, or touch anything outside this repo. ## Auto mode — how the other skills run here Autopilot drives **map**, **feature**, and *...