sddp-autopilot
Skill98 starsChanged 28 days agoMITView on GitHub
Run the full SDD feature-delivery pipeline.
In this repository73 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- sddp-amendSkill
- sddp-analyzeSkill
- sddp-autopilotSkill
- sddp-checklistSkill
- sddp-clarifySkill
- sddp-devopsSkill
- sddp-devsetupSkill
- sddp-implement-qc-loopSkill
- sddp-implementSkill
- sddp-initSkill
- sddp-planSkill
- sddp-prdSkill
- sddp-projectplanSkill
- sddp-qcSkill
- sddp-regenSkill
- sddp-reverseengineerSkill
- sddp-specifySkill
- sddp-systemdesignSkill
- sddp-tasksSkill
- sddp-amendSkill
- sddp-analyzeSkill
- sddp-checklistSkill
- sddp-clarifySkill
- sddp-devopsSkill
- sddp-devsetupSkill
- sddp-implement-qc-loopSkill
- sddp-implementSkill
- sddp-initSkill
- sddp-planSkill
- sddp-prdSkill
- sddp-projectplanSkill
- sddp-qcSkill
- sddp-regenSkill
- sddp-reverseengineerSkill
- sddp-specifySkill
- sddp-systemdesignSkill
- sddp-tasksSkill
- adr-authoringSkill
- artifact-conventionsSkill
- clarification-strategiesSkill
- compact-communicationSkill
- evidence-led-authoringSkill
- implementation-standardsSkill
- instructions-managementSkill
- markdown-compressionSkill
- plan-authoringSkill
- quality-assuranceSkill
- sdd-methodologySkill
- sddp-amendSkill
- sddp-analyzeSkill
- sddp-autopilotSkill
- sddp-checklistSkill
- sddp-clarifySkill
- sddp-devopsSkill
- sddp-devsetupSkill
- sddp-implement-qc-loopSkill
- sddp-implementSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
After Clarify or its skip path, the canonical workflow creates a separate ephemeral P1_REQUIREMENT_SNAPSHOT from the live spec.md.
- Distinctive: line 26
When any sub-skill says Delegate, use the Task tool to invoke the corresponding sub-agent:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
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:
- Specify →
.github/sddp/workflows/specify-feature/WORKFLOW.md - Clarify →
.github/sddp/workflows/clarify-spec/WORKFLOW.md - Plan →
.github/sddp/workflows/plan-feature/WORKFLOW.md - Checklist →
.github/sddp/workflows/generate-checklist/WORKFLOW.md(looped until queue exhausted) - Tasks →
.github/sddp/workflows/generate-tasks/WORKFLOW.md - Analyze →
.github/sddp/workflows/analyze-compliance/WORKFLOW.md - Implement+QC →
.github/sddp/workflows/implement-qc-loop/WORKFLOW.md
When any sub-skill says Delegate, use the Task tool to invoke the corresponding sub-agent:
- Delegate: Context Gatherer → delegate to
sddp-context-gatherer - Delegate: Task Tracker → delegate to
sddp-task-tracker - Delegate: Developer → delegate to
sddp-developer - Delegate: Checklist Reader → delegate to
sddp-checklist-reader - Delegate: Test Evaluator → delegate to
sddp-test-evaluator - Delegate: Technical Researcher → delegate to
sddp-technical-researcher - Delegate: QC Auditor → delegate to
sddp-qc-auditor - Delegate: Story Verifier → delegate to
sddp-story-verifier - Delegate: Policy Auditor → delegate to
sddp-policy-auditor - Delegate: Test Planner → delegate to
sddp-test-planner - Delegate: ADR Author → delegate to
sddp-adr-author - Delegate: Adversarial Scanner → delegate to
sddp-adversarial-scanner - Delegate: API Designer → delegate to
sddp-api-designer - Delegate: Database Administrator → delegate to
sddp-database-administrator - Delegate: Requirements Scanner → delegate to
sddp-requirements-scanner - Delegate: WBS Generator → delegate to
sddp-wbs-generator - Delegate: Spec Validator → delegate to
sddp-spec-validator - Delegate: Plan Validator → delegate to
sddp-plan-validator - Delegate: Tasks Validator → delegate to
sddp-tasks-validator
AUTOPILOT = true for all phases. At every user interaction point, choose the recommended default and log the decision — never prompt the user.
Report compact progress at each phase boundary — completed phase, blocker delta, next phase. Only halt for the conditions defined in the pipeline skill.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

