ai-autopilot

# Autopilot v2 ## Purpose Autonomous execution of large approved specs via a 6-phase pipeline. Decomposes a spec into N focused sub-specs, deep-plans each with parallel agents, orchestrates a dependency-aware execution DAG, implements in waves, runs a single final verify+guard+review pass with one bounded quality-remediation pass on the full changeset, and delivers the full changeset via PR with a transparency report. Execution is not complete until sub-spec work converges into a final delivery PR against protected main. One invocation, zero interruptions, full disclosure. ## When to Use - Spec has >= 3 independent concerns or touches >= 10 files - After `/ai-brainstorm` approval (spec.md exists and is not a placeholder) - Backlog runs with `--backlog --source <github|ado|local>` to absorb GitHub issues, Azure Boards items, or markdown task lists into the DAG (D-127-12; replaces the legacy `/ai-run` skill) - When manual `/ai-build` would overflow context within a single session - Multi-concern work that benefits from parallel intelligence gathering and DAG-driven execution ## When NOT to Use - < 3 concerns -- use `/ai-build` directly (autopilot overhead not justified) - Draft or unapproved spec -- run `/ai-brainstorm` first - Need human review between phases -- use `/ai-build` with manual checkpoints - Cross-repo changes -- coordinate manually - Data migrations with destructive DDL -- require explicit user approval per step ## Process **Step 0 — Validate**: confirm `....