forge-autopilotlisted

# forge-autopilot — bounded autonomous pipeline execution Autopilot walks the pipeline for the user: for each planned stage it runs that stage's agent, checks the stage gate, and **advances only on a pass** — **stopping at the first blocker** instead of forcing past it. It generalizes `/forge:force-advance` (one gated advance) and `/forge:build --milestone` (a within-stage batch) to a cross-stage loop. The plan is computed deterministically by `scripts/autopilot.py`; this skill executes it in-session (a script can't drive the Agent tool — ADR-006). ## When to Use - `/forge:autopilot` (optionally `to stage N`, `the next K stages`, or `until a gate`). - The user wants several stages run without issuing each `/forge:*` command by hand. - `/forge:autopilot --unattended` for a fully hands-free run (no checkpoints; see below). ## When NOT to Use - A single stage → just run that stage's command (e.g. `/forge:build`). - The user wants to override a known blocker → that's `/forge:force-advance`, not autopilot. ## Safety rails (always) - **Bounded self-heal, then stop-on-gate.** On a blocking gate failure, autopilot makes a bounded number of fix attempts via `/forge:resolve` (`autopilot.max_heal_attempts`, default **1**; `0` restores classic stop-on-gate), re-checking the gate after each. When heal is exhausted (or disabled) and blockers remain it STOPS and surfaces them. It **never** force-advances unless `.forge/config.yaml` → `autopilot.allow_force: true` **and** t