spec-driven-development
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use…
What it does
- 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
- Always do: Run tests before commits, follow naming conventions, validate inputs
- Ask first: Database schema changes, adding dependencies, changing CI config
Requirements & configuration
- [Anything unresolved that needs human input]
- No task should require changing more than ~5 files
- Update when decisions change — If you discover the data model needs to change, update the spec first, then implement.
- | "This is simple, I don't need a spec" | Simple tasks don't need long specs, but they still need acceptance criteria. A two-line spec is fine. |
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
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.
Source
Repository: https://github.com/addyosmani/agent-skills
spec-driven-development FAQ
What does the spec-driven-development skill do?
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. Starting a new project or feature Requirements are ambiguous or incomplete
What does spec-driven-development require?
[Anything unresolved that needs human input] No task should require changing more than ~5 files Update when decisions change — If you discover the data model needs to change, update the spec first, then implement. | "This is simple, I don't need a spec" | Simple tasks don't need long specs, but they still need acceptance criteria. A two-line spec is fine. |
How do I install spec-driven-development?
Run: npx -y skills add https://github.com/addyosmani/agent-skills --skill spec-driven-development --agent claude-code — the source lives at github.com/addyosmani/agent-skills.
Maintain spec-driven-development?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[](https://getagentictools.com/skills/addyosmani-agent-skills-spec-driven-development?ref=badge) npx agentictools info skills/addyosmani-agent-skills-spec-driven-development The second line is the CLI lookup for this page — handy in READMEs and docs.