Creates specs before coding.
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.This is the skill's description: the text your AI reads to decide when the skill applies.
addy-spec-driven-development/SKILL.md
---
name: spec-driven-development
description: Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
---
# Spec-Driven Development
## Overview
Write a structured specification before writing any code. The spec is the shared source of truth between you and the human engineer — it defines what we're building, why, and how we'll know it's done. Code without a spec is guessing.
## When to Use
- Starting a new project or feature
- Requirements are ambiguous or incomplete
- The change touches multiple files or modules
- You're about to make an architectural decision
- The task would take more than 30 minutes to implement
**When NOT to use:** Single-line fixes, typo corrections, or changes where requirements are unambiguous and self-contained.
## The Gated Workflow
Spec-driven development has four phases. Do not advance to the next phase until the current one is validated.
… load the full skill through Skill Me