sddp-autopilot · git:20260821.a60b53a · 2026-08-21 · sha256 2c89490d05c662a6

sddp-autopilot git:20260821.a60b53aA

Immutable. This exact content never changes and is served at /api/v1/blob/2c89490d05c662a6.

---
name: sddp-autopilot
description: "Run the full SDD feature-delivery pipeline. Direct command-bar dispatch only; do not select for general queries."
---
Argument hint: `[optional: feature description; omit to select the first unchecked epic]`
Command category: `orchestration`
Prerequisites: `autopilot:enabled`, `product-document:planning-ready`, `technical-context:planning-ready`

You are running the **Autopilot Pipeline** — a fully automated SDD workflow that executes all phases (Specify → Clarify → Plan → Checklist → Tasks → Analyze → Implement+QC) in a single uninterrupted turn without user interaction. Every decision point, phase lifecycle event (start, complete, skip), gate check, and halt is logged to `autopilot-log.md` using a structured 7-column schema (`Timestamp | Phase | Event | Detail | Outcome | Rationale | Artifacts`). Every artifact or document mentioned in a log row must appear as a clickable relative Markdown link in the Artifacts column. At run end, a `## Run Summary` section is appended with per-phase status and links to final artifacts.

Autopilot is real unattended execution, not a demo, showcase, dry run, or simulation.
Execute each phase for real: perform actual file edits, actual build/test/lint/QC commands, and create artifacts only when the owning phase has genuinely completed.
Never simulate implementation, QC, test results, or marker creation. If real execution cannot complete in the current environment, halt and report the blocker.

Load and follow the workflow in `.github/sddp/workflows/autopilot-pipeline/WORKFLOW.md`.
Retain the initial full Context Gatherer report as `PIPELINE_CONTEXT` and pass it unchanged to every inline phase; downstream phases re-check mutable artifacts instead of delegating Context Gatherer again.
After Clarify or its skip path, the canonical workflow creates a separate ephemeral `P1_REQUIREMENT_SNAPSHOT` from the live `spec.md`; it is not part of `PIPELINE_CONTEXT` and is passed only to Tasks and fresh Implement+QC gates after checksum verification.

The pipeline skill will instruct you to load and execute these sub-skills inline, in order:
1. **Specify** → `.github/sddp/workflows/specify-feature/WORKFLOW.md`
2. **Clarify** → `.github/sddp/workflows/clarify-spec/WORKFLOW.md`
3. **Plan** → `.github/sddp/workflows/plan-feature/WORKFLOW.md`
4. **Checklist** → `.github/sddp/workflows/generate-checklist/WORKFLOW.md` (looped until queue exhausted)
5. **Tasks** → `.github/sddp/workflows/generate-tasks/WORKFLOW.md`
6. **Analyze** → `.github/sddp/workflows/analyze-compliance/WORKFLOW.md`
7. **Implement+QC** → `.github/sddp/workflows/implement-qc-loop/WORKFLOW.md`

When any sub-skill says **Delegate**, read the exact referenced sub-agent file **at that point, not before**, then perform the delegated task yourself.

**AUTOPILOT = true** for all phases. At every user interaction point, choose the recommended default and log the decision — never prompt the user.

Report progress at each phase boundary. Only halt for the conditions defined in the pipeline skill.