Spec-Driven Development

by addyosmani

Spec-Driven Development is an AI Engineering skill for Claude Code, published by addyosmani in agent-skills.

86.7K stars9.3K forkson addyosmani/agent-skillsAdded 2026/08/13Repository updated 2026/08/11

View source on GitHub Download repo ZIP

agent-skillsantigravityclaude-codecodexcursorskills

Install in seconds

Install Spec-Driven Development

Copy Spec-Driven Development into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/addyosmani/agent-skills/tree/main/skills/spec-driven-development ~/.claude/skills/spec-driven-development

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/addyosmani/agent-skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/spec-driven-development/SKILL.md in addyosmani/agent-skills
Installs to: ~/.claude/skills/spec-driven-development
Collection: One of 24 skills cataloged from this repository
Category: AI Engineering — 2451 skills

What Spec-Driven Development does

Spec-Driven Development writes a structured specification before coding, defining objective, commands, code style, testing strategy, and boundaries. Use it when starting a new project or feature, when requirements are ambiguous, or when a change touches multiple files.

Spec-Driven Development is cataloged under AI Engineering on DirSkills. Spec-Driven Development comes from a repository tagged agent-skills, antigravity, claude-code, codex and cursor.

Documentation

README

Excerpt

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.

This is the opening of the README. Read the full README on GitHub.

Commands Spec-Driven Development provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

/plan
/build

Frequently asked about Spec-Driven Development

What else does addyosmani publish alongside Spec-Driven Development?
Spec-Driven Development is one of 24 skills that DirSkills catalogs from addyosmani/agent-skills, the repository it ships in. Its siblings there include API and Interface Design, Agent Skill Discovery and Browser Testing. Each one is a separate skill with its own page in this directory, installs the same way Spec-Driven Development does, and is maintained by addyosmani in that same repository. The rest of the collection is listed on the addyosmani/agent-skills page.
How does Spec-Driven Development compare to other AI Engineering skills?
Spec-Driven Development ranks #55 by stars among the 2451 AI Engineering skills in this catalog. The most-starred ones next to it are Architecture Decision Records, AI-First Engineering and Agentic OS. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Spec-Driven Development against them. Open each page to compare what they document and how they install.