sdd-tasks
Skill11 starsChanged 10 days agoMITView on GitHub
Break an approved plan into tasks.md, or extract the next task to implement.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- GabrielaStark/starktheir own version, first seen Nov 1, 2026
- svg153/skillstheir own version, first seen Nov 1, 2026
- monaccode/astromesh-sddtheir own version, first seen Oct 20, 2026
- PedroMosquera/squadaitheir own version, first seen Oct 13, 2026
- felipefontoura/pi-sdd-kittheir own version, first seen Oct 13, 2026
- pchemguy/Skill-SDD-Managertheir own version, first seen Oct 6, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- felipefontoura/pi-sdd-kit★ 36same name
- khangpqvn/SDDADD★ 12same name
- PedroMosquera/squadai★ 10same name
- GabrielaStark/SDD★ 1same name
- GabrielaStark/stark★ 1same name
- Maicololiveras/praxisgenai-agent-orchestrator★ 1same name
- svg153/skills★ 1same name
- callingcard1973/claude-skills★ 0same 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-planSkill
- sdd-researchSkill
- sdd-specifySkill
- sdd-statusSkill
- sdd-validateSkill
- spec-driven-developmentSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 0 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
5
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, sections "Phase 3" and "Phase 4".
- Very specific: line 14
Use "Task Breakdown Prompt" and "Task Validation Prompt" in ../spec-driven-development/references/prompt-patterns.md.
- Very specific: line 15
Use the template under "tasks.md Template" in ../spec-driven-development/references/artifact-templates.md.
- Very specific: line 17
Ask which: break down the plan, or take the next task.
“Common” is measured: kept by at least 6 in 10 of the 7 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-tasks
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, sections "Phase 3" and "Phase 4".
Use "Task Breakdown Prompt" and "Task Validation Prompt" in ../spec-driven-development/references/prompt-patterns.md.
Use the template under "tasks.md Template" in ../spec-driven-development/references/artifact-templates.md.
Ask which: break down the plan, or take the next task.
Breakdown produces tasks.md. Gate: "Gate 3" in ../spec-driven-development/references/quality-gates.md.
Next task: read "Single Task Implementation Prompt" in the prompt file, extract one open task with its ACs and contract, implement it, then run "Gate 4".
Gate 4 checker: "green" is not evidence. Require the failing-before run with its failure quoted. A test that asserts on data it built itself or never calls the code under test cannot fail: replace or delete it and record its AC as unproven, never keep it as coverage. Show what a valid proof calls and asserts. The verdict is fail or inconclusive for those ACs, never pass.
Validate: node ../spec-driven-development/scripts/sdd-check.mjs specs/<feature>
Next: /sdd-validate when all tasks are done.
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.