Specification-Driven Development

Coordinate four-phase specification workflows from analysis to execution.

1|Updated Jan 1, 2026

Search Tags:#workflow #documentation #specification #task-management #quality-gates #decompose #first-principles

Ready to run

npx skills add https://github.com/betamatt/claude-plugins --skill specification-driven-development

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Specification-Driven Development
Source: https://github.com/betamatt/claude-plugins/tree/main/spec/skills/spec-methodology
Command: npx skills add https://github.com/betamatt/claude-plugins --skill specification-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Specification-first approaches help reduce rework and misalignment by starting with a clear, testable contract before building software.

Core Features & Use Cases

Phase-based spec workflow: Create (/spec:create), Validate (/spec:validate), Decompose (/spec:decompose), Execute (/spec:execute) with formal gates.
Quality gates and task management integration: ensures specs meet quality criteria and tasks are tracked in STM or TodoWrite.
Content preservation and risk mitigation: copy details into tasks to prevent information loss and scope creep.

Quick Start

Create a complete specification draft for a new feature using the four-phase methodology and prepare a task breakdown.

Frequently Asked Questions about Specification-Driven Development

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

FAQPage Schema

What is specification-driven development and how does it reduce software rework?▼

This specification workflow guides software development from problem analysis to execution through a structured four-phase process. It includes creating specs, validating design intent, decomposing work into tasks, and orchestrating implementation using formal quality gates.

How do I decompose software requirements into manageable development tasks?▼

Use the four-phase spec workflow to decompose software requirements: Create, Validate, Decompose, and Execute. This methodology breaks specs into tracked tasks using STM or TodoWrite, applying formal quality gates to ensure criteria are met before execution.

Can I integrate specification workflows with task-management tools like TodoWrite?▼

Yes, specification workflows integrate directly with task-management tools like STM and TodoWrite. Quality gates ensure specs meet criteria while tracking decomposed tasks, copying specification details into tasks to prevent information loss during execution.

What's the best way to validate design intent before starting software implementation?▼

The best way to validate design intent is through a dedicated validation phase with formal quality gates. This ensures your specification draft meets quality criteria and establishes a testable contract before you decompose work and begin implementation.

When should I not use a specification-first approach for software development?▼

You should avoid specification-first development for rapid prototyping or exploratory work where requirements are completely unknown. The formal quality gates and four-phase process enforce structure that may slow down highly experimental or spike-based development efforts.