spec-driven-development

Create structured specifications and technical plans before implementation.

Updated Apr 19, 2026

Search Tags:#workflow #planning #tdd #development #architecture #specification

Ready to run

npx skills add https://github.com/dmarins/sdd --skill spec-driven-development-dmarins

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/dmarins/sdd/tree/main/skills/spec-driven-development
Command: npx skills add https://github.com/dmarins/sdd --skill spec-driven-development-dmarins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of ambiguous requirements and architectural drift by enforcing a structured specification process before any code is written, ensuring alignment between human intent and technical implementation.

Core Features & Use Cases

Structured Specification: Provides a standardized template for defining project goals, tech stacks, project structure, and success criteria.
Workflow Gates: Implements a rigorous four-phase process (Specify, Plan, Tasks, Implement) that requires human validation at each stage.
Use Case: Use this when starting a new feature or complex refactor to define clear acceptance criteria and technical boundaries, preventing scope creep and reducing the need for rework.

Quick Start

Initiate the development process by asking the agent to create a new specification document based on the project requirements.

Frequently Asked Questions about spec-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is a structured specification workflow in software development?▼

It standardizes the software development lifecycle by mandating structured specifications and technical plans before implementation, ensuring alignment between human intent and code to prevent architectural drift and scope creep.

How do I prevent scope creep when developing a complex feature?▼

You prevent scope creep by enforcing a gated workflow with four phases: Specify, Plan, Tasks, and Implement. This requires explicit human validation at each checkpoint to define clear acceptance criteria and technical boundaries.

How do I create a technical plan for a complex software refactor?▼

You create a technical plan by defining project goals, tech stacks, project structure, and success criteria in a standardized specification document. Break down implementation into iterative tasks following human validation of the plan.

Can I use a specification-driven approach for TDD and architectural decision-making?▼

Yes, specification-driven development facilitates TDD and architectural decision-making by breaking down complex features into structured specifications and iterative execution tasks before writing code, ensuring technical boundaries are defined.

Does this structured development workflow require manual validation?▼

Yes, the workflow requires explicit human validation at each of the four development checkpoints: specification, planning, task breakdown, and iterative execution, ensuring adherence to defined project documentation standards.

When should I avoid using a specification-driven development workflow?▼

Avoid this workflow for simple tasks lacking complex feature development or architectural decision-making requirements, as the mandatory structured specifications and gated human validation process introduces overhead suited for preventing ambiguous requirements.