SPEC-DRIVEN DEVELOPMENT
Purpose first. Then, development.
Spec-Driven Development (SDD) organizes work around a clear description of expected behavior. The specification explains what to solve and why; the plan describes how to implement it.
A workflow with visible decisions
- 01
Agree on principles
Define the architecture, quality and security rules the project must follow.
- 02
Specify
Describe users, scope, requirements and observable acceptance criteria. Resolve questions affecting scope.
- 03
Plan
Choose components, interfaces, data, dependencies, tests and deployment within project constraints.
- 04
Break down tasks
Prepare small actions linking each change to a requirement and a way to verify it.
- 05
Implement and verify
Build, run tests and review results against the specification. Update documents when decisions change.
What it helps with
It makes agreements explicit, helps reveal ambiguities before implementation and supports reviewing whether the result meets the stated need.
How this generator applies it
SDD Generator prepares a document foundation for team review. It uses your answers; unanswered fields remain open items and technical decisions must be adapted to your project.
| Document | What you use it for |
|---|---|
| spec.md | The problem, scope, requirements and acceptance criteria. |
| plan.md | The technical proposal, testing and deployment. |
| tareas.md | Initial work linked to RF, RNF and RS. |
| ADRs and risk analysis | Proposed decisions and risks requiring assessment. |
| Checklists and evidence | Reviews and tests the team still needs to complete. |
A brief example
Need: run backups without a daily manual action.
RF-001: the system must back up selected directories at the configured time.
Criterion: given an accessible source, when the scheduled time arrives, then a backup is created and its location reported.
Plan: a script validates paths, creates the archive and logs the result.
Task: write success and invalid-source tests before implementing the backup.
After downloading
Review spec.md and PENDIENTES.md, agree scope with the team, adapt the constitution and plan, then complete approvals, tests and evidence before production deployment.