sdd-plan
Skill4 starsChanged 22 days agoMITView on GitHub
Convierte una spec aprobada en specs/NNN/plan.md (módulos, datos, contrato, decisiones y estrategia de tests) y specs/NNN/tasks.md (tareas pequeñas en orden, cada una con sus RF y un "Hecho cuando" verificable). Usar después de aprobar la spec. Sin código.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- mariano-aguero/spec-driven-development-skilltheir own version, first seen Nov 8, 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-specify.
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-specify
Use when creating, reviewing, or revising docs/dev/SPEC.md, focused specification children, or FEATURE-SPEC.md; defining required software behavior, interfaces, data contracts, error semantics, invariants, and objective acceptance for a new or existing system.
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
- mariano-aguero/spec-driven-development-skill★ 11same 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 repository10 other files it gives its agents.
- core/AGENTS.mdAGENTS.md
- skills/sdd-init/templates/AGENTS.mdAGENTS.md
- skills/sdd-init/templates/CLAUDE.mdCLAUDE.md
- nombre-de-la-skillSkill
- handoffSkill
- sdd-changeSkill
- sdd-implementSkill
- sdd-initSkill
- sdd-specSkill
- sdd-validateSkill
The file
Files
<!-- Basado en hello-sdd de MoureDev (Apache-2.0), adaptado. Ver NOTICE. -->Plan y tareas
No escribas código. La spec dice el qué; aquí se decide el cómo y el orden.
Plan
- Lee la spec. Si no está aprobada o quedan
[NECESITA ACLARACIÓN], vuelve asdd-spec. - Antes de decidir una librería o un patrón, comprueba si ya existe en el repo y qué dice la documentación oficial de la versión en uso.
- Escribe
specs/NNN/plan.mdcon: módulos y el RF que cubre cada uno, modelo de datos con un ejemplo, contrato (comandos, endpoints, errores), decisiones técnicas con la alternativa descartada, y estrategia de tests con los comandos que formaránscripts/verify.sh. - Si encuentras algo que la spec no decide, dilo. No lo rellenes tú.
Tareas
- Escribe
specs/NNN/tasks.md: tareas de 20-30 minutos, en orden de dependencia, con checkbox, los RF que cubren y una línea "Hecho cuando:" verificable. - Cada RF aparece en al menos una tarea. La primera deja el esqueleto y
verify.shcon sus pasos reales; la última es la validación. - Aprobación. Con el sí del usuario, escribe
Estado: aprobados ◆2 (fecha)en los dos ficheros. Siguiente fase:sdd-implement.
- [ ] T1. Esqueleto del proyecto. (RF: —) Hecho cuando: la suite de tests corre.
- [ ] T2. <pieza concreta>. (RF-2, RF-3) Hecho cuando: tests de <escenarios> en verde.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.