spec-driven-development

Enforces strict Spec-Driven Development. Prevents direct coding and ensures spec → generate → review loops.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026

When & Why to Use This Skill

This Claude skill enforces a rigorous Spec-Driven Development (SDD) framework, transforming the AI from a simple coder into a disciplined software engineer. By mandating a 'spec → generate → review' workflow, it ensures that all code modifications are rooted in comprehensive documentation, eliminating manual errors and maintaining the specification as the single source of truth for the entire codebase.

Use Cases

  • New Feature Development: Systematically building complex features by first defining requirements in spec.md and task lists to ensure the generated code aligns perfectly with business logic.
  • Architectural Planning: Utilizing ADRs (Architectural Decision Records) and plan.md to map out system changes before execution, preventing technical debt and architectural drift.
  • Codebase Refactoring: Managing large-scale refactors by updating specifications first, allowing Claude to regenerate consistent code across multiple files based on the new design.
  • Quality Assurance & Compliance: Ensuring that every line of code has a corresponding specification entry, providing a clear audit trail for regulated industries or high-stakes software projects.
namespec-driven-development
descriptionEnforces strict Spec-Driven Development. Prevents direct coding and ensures spec → generate → review loops.

Spec-Driven Development Rules

Golden Rule

Never write or modify code directly. All changes must originate from specifications.

Mandatory Workflow

  1. Analyze requirement
  2. Write or update spec (Markdown)
  3. Generate code via Claude Code
  4. Review output
  5. Refine spec if needed
  6. Regenerate

Required Spec Artifacts

Depending on feature scope:

  • spec.md
  • plan.md
  • tasks.md
  • checklist.md
  • ADR (if architectural)

Forbidden Actions

  • Manual code patches
  • Guessing requirements
  • Skipping specification step

Success Criteria

  • Specs are the single source of truth
  • Code exactly matches specs