sdd-validate
Skill4 starsChanged 22 days agoMITView on GitHub
Comprueba que lo construido cumple la spec, requisito a requisito, con el test que lo cubre y el resultado de ejecutarlo, más scripts/verify.sh y la regresión de specs anteriores. Usar cuando todas las tareas de una spec estén marcadas.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- mariano-aguero/spec-driven-development-skilltheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- mariano-aguero/spec-driven-development-skill★ 11same 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-planSkill
- sdd-specSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
No arregles nada aquí: se comprueba y se informa.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
<!-- Basado en hello-sdd de MoureDev (Apache-2.0), adaptado. Ver NOTICE. -->Validar una spec
No arregles nada aquí: se comprueba y se informa.
Proceso
- Recorre la spec RF por RF. Para cada uno: qué test lo cubre, ejecútalo y anota el resultado. Un RF sin test, o con un test que no se ejecutó, es no cumplido.
- Ejecuta
scripts/verify.shcompleto, con todas las specs anteriores dentro. Si una spec ya aceptada se rompe, la validación no pasa. - Revisa los criterios de finalización y la sección "Fuera de alcance": que no se haya construido nada que no se pidió.
- Escribe
specs/NNN/validacion.mdcon la tabla RF → test → resultado y un veredicto: cumplida o no cumplida, con lo que falta. - Aceptación. Enseña el informe al usuario. Con su sí, escribe
Estado: aceptada ◆3 (fecha)en la spec.
Un fallo vuelve a sdd-implement si el código no cumple, o a sdd-change si es la spec la que estaba mal.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.