Menu
Usar cuando se escribe, valida o implementa una spec ejecutable SDD.
| name | spec-driven-development |
| description | Usar cuando se escribe, valida o implementa una spec ejecutable SDD. |
| summary | Genera specs ejecutables. Flujo: analyst->architect->spec-writer->developer->test. Input: Task ADO. |
| maturity | stable |
| context | fork |
| context_cost | high |
| agent | business-analyst |
| category | sdd-framework |
| tags | ["sdd","specs","development","agents"] |
| priority | high |
| trigger | {"keywords":["spec","sdd","especificacion ejecutable","specification"]} |
If you were dispatched as a subagent to execute a specific delegated task, skip this skill's full orchestration workflow. Execute only the assigned task, report result (DONE / DONE_WITH_CONCERNS / BLOCKED), and return. This guard prevents runaway skill activation in nested agent contexts.
Transforma Tasks de Azure DevOps en Specs ejecutables por un Developer humano o un agente Claude.
Prerequisitos: ../azure-devops-queries/SKILL.md, ../pbi-decomposition/SKILL.md
PBI → Tasks → Specs (SDD) → Implementación (Human | Agent) → Code Review → Done
Un Developer puede ser:
| Tipo | Cuándo usar |
|---|---|
human | Lógica compleja, decisiones arquitectónicas, ambigüedad alta |
agent-single | Tasks bien definidas, patrones repetitivos, boilerplate |
agent-team | Tasks grandes (>6h) que benefician de paralelización |
curl -s -u ":$PAT" "$AZURE_DEVOPS_ORG_URL/{proyecto}/_apis/wit/workitems/{id}?api-version=7.1" | jq .
find src -name "*{patrón}*" | head -5
Guardar en: projects/{proyecto}/specs/{sprint}/AB{id}-{tipo}-{desc}.spec.md
Usar plantilla: references/spec-template.md
Una Spec es ejecutable cuando:
Si NO cumple → developer_type: human
Escribir: projects/{proyecto}/agent-notes/{ticket}-legacy-analysis-{fecha}.md
Ejecutar /security-review {spec} — security-guardian revisa contra OWASP Top 10. Si issues 🔴 → corregir spec antes de implementar. Obligatorio para: auth, pagos, datos personales, APIs públicas, infraestructura.
test-engineer escribe tests que fallan (Red)projects/{proyecto}/agent-notes/{ticket}-test-strategy-{fecha}.mdDetalles: references/agent-invocation.md (contexto, prompts, logging, agent-notes)
Detalles: references/review-metrics.md (review checklist, Azure DevOps update, metricas SDD, mejora continua)
Formato delta (ADDED/MODIFIED/REMOVED) en lugar de reescribir. Consolidar con /spec-verify al cerrar sprint. Detalle: @references/compliance-matrix.md
Templates: references/spec-template.md · references/layer-assignment-matrix.md · references/compliance-matrix.md | Execution: references/agent-invocation.md · references/review-metrics.md | Comandos: /spec-generate, /spec-implement, /spec-review, /spec-verify
Ver satélite: REFERENCE.md — anti-patterns de AC no verificables y merge sin aprobación humana (SE-210).
Strips all sugar-coating and marketing. Gives the brutally honest truth in the fewest possible words. Use when you suspect self-deception, before committing, or before shipping.
Adversarial review that hunts every weakness, assumption, edge case, and missing test. Opponent mode — finds what will break before it breaks in production. Use when merging, when reviewing security-critical code, or when the solution feels too simple.
Usar cuando se lee, escribe, busca o consolida la memoria persistente entre sesiones de Savia.
Test-driven development with vertical-slice red-green-refactor cycles. Use when applying TDD to a new feature or bug fix, when user mentions 'red-green-refactor', 'tdd', 'test-first', 'vertical slice' — explicitly avoids the 'horizontal slicing' anti-pattern (write all tests first, then all code) which produces brittle implementation-coupled tests.
TEMPLATE — copia este directorio para crear una skill nueva. NO se carga en runtime.
Elevates perspective from trees to forest. Maps architecture, dependencies, and second-order effects before implementation decisions. Use when designing, when evaluating trade-offs, or at the start of design sessions.