sdd-plan
Skill11 starsChanged 10 days agoMITView on GitHub
Turn an approved spec into plan.md, data-model.md, and contracts.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- ad1code/sdd-harnesstheir own version, first seen Nov 1, 2026
- monaccode/astromesh-sddtheir own version, first seen Oct 20, 2026
- felipefontoura/pi-sdd-kittheir own version, first seen Oct 13, 2026
- pchemguy/Skill-SDD-Managertheir own version, first seen Oct 6, 2026
- khangpqvn/SDDADDtheir own version, first seen Sep 29, 2026
Used with
Projects with it also use sdd-implement.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
pchemguySkillsdd-implement
Use when selecting an executable task range, or executing or resuming a bounded SDD implementation workflow driven by TASKS or FEATURE-TASKS, completing pending task work, coordinating tests and documentation, verifying results, marking completion, committing and pushing each task, or stopping at a requested checkpoint.
Also in 3 projects that use this
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- felipefontoura/pi-sdd-kit★ 36same name
- khangpqvn/SDDADD★ 12same name
- ad1code/sdd-harness★ 4same name
- monaccode/astromesh-sdd★ 0same name
- pchemguy/Skill-SDD-Manager★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- sdd-changeSkill
- sdd-initSkill
- sdd-researchSkill
- sdd-specifySkill
- sdd-statusSkill
- sdd-tasksSkill
- sdd-validateSkill
- spec-driven-developmentSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read ../spec-driven-development/SKILL.md, section "5-Phase Workflow".
- Very specific: line 13
Read ../spec-driven-development/references/workflow-phases.md, section "Phase 2".
- Very specific: line 14
Use "Technical Plan Generation Prompt" and "Plan Review Prompt" in ../spec-driven-development/references/prompt-patterns.md.
- Very specific: line 15
Use the templates under "plan.md Template", "data-model.md Template" and "contracts/[endpoint].md Template" in …
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
sdd-plan
Paths below are relative to this file. Resolve them before running anything.
Read ../spec-driven-development/SKILL.md, section "5-Phase Workflow".
Read ../spec-driven-development/references/workflow-phases.md, section "Phase 2".
Use "Technical Plan Generation Prompt" and "Plan Review Prompt" in ../spec-driven-development/references/prompt-patterns.md.
Use the templates under "plan.md Template", "data-model.md Template" and "contracts/[endpoint].md Template" in ../spec-driven-development/references/artifact-templates.md.
Needs: spec.md with Status Approved, and constitution.md.
Open [NEEDS CLARIFICATION] items in spec.md block this phase: name each and why it changes the architecture, and offer /sdd-specify to clarify. If the user insists, proceed: replace each marker in spec.md with an explicit Assumption: line, then report the Gate 1 verdict with the failing checks named.
Produce: plan.md, data-model.md, contracts/.
Gate: "Gate 2" in ../spec-driven-development/references/quality-gates.md.
Validate: node ../spec-driven-development/scripts/sdd-check.mjs specs/<feature>
Next: /sdd-tasks.
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.