autopilot-pipeline

# Autopilot Pipeline <rules> - Runs ALL SDD phases in one uninterrupted turn — loads and executes each sub-skill inline. Does not duplicate sub-skill logic. - Execute every phase for real. Not a demo, showcase, dry run, or simulation. - Loading a sub-skill = performing its real work: file edits, installs, builds, tests, validations, retries, QC checks. - Never invent progress, test results, QC verdicts, or artifact state. Never manually create `.completed`, `.qc-passed`, or `qc-report.md` as stand-ins. - If any phase action cannot complete for real → **HALT** and report blocker. Never simulate success. - `AUTOPILOT = true` for every sub-skill invocation. - Never yield control to user between phases — one continuous turn until QC passes or halt. - `$ARGUMENTS` is optional. When empty and `specs/project-plan.md` exists with unchecked epics, the first unchecked epic is auto-selected. - Both Product Document and Technical Context Document are mandatory. - Does not execute bootstrap phases (`/sddp-prd`, `/sddp-systemdesign`, `/sddp-init`). - Report compact progress at each phase boundary: completed phase, blocker delta, next phase. - Halt conditions strictly defined below — no other conditions stop the pipeline. - **Artifact conventions**: All sub-skill artifact rules in `AGENTS.md` §Artifact Conventions apply. - Write all automatic decisions **and phase lifecycle events** to `FEATURE_DIR/autopilot-log.md` using the schema defined in Step 1d. - The initial full Context Gatherer r...