spec-driven-development

Write specifications defining goals, constraints, and acceptance criteria before coding.

Updated Jun 27, 2026

Search Tags:#code quality #project management #specification #developer efficiency #software development process

Ready to run

npx skills add https://github.com/coff33ninja/ai-skills-mcp --skill spec-driven-development-coff33ninja

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the misdirection of effort by ensuring a specification is written before implementing code changes, defining goals, inputs/outputs, constraints, and acceptance criteria.

Core Features & Use Cases

Spec Writing: Encourages writing a concise spec for each non-trivial feature, refactor, or bug fix.
User Confirmation: Requires confirmation from the user before proceeding with implementation.
Implementation Against Spec: Directs implementation strictly against the agreed-upon specification.
Verification: Ensures the final outcome meets all acceptance criteria.

Quick Start

Use the spec-driven-development skill to define the spec for a new feature 'Implement user authentication'.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

What is specification-driven software development and when should I use it?▼

Specification-driven software development is a process where you define goals, inputs, outputs, and constraints before coding begins. You should use it for non-trivial feature development, complex code refactoring, and bug fixes to prevent misdirected effort.

How do I write a specification for a new feature before coding?▼

To write a specification for a new feature, define the goals, inputs, outputs, constraints, and acceptance criteria. This process requires user confirmation on the defined scope before any implementation work begins, ensuring alignment.

Does specification-driven development work for code refactoring and bug fixes?▼

Yes, specification-driven development works for code refactoring and bug fixes. It ensures all requirements and constraints are defined and agreed upon before coding begins, directing implementation strictly against the agreed-upon specification.

What is the best way to ensure code quality during complex feature development?▼

The best way to ensure code quality during complex feature development is implementing against a pre-defined specification. This approach ensures the final outcome meets all acceptance criteria through verification after strict implementation.

Why does software development effort get misdirected without a specification?▼

Software development effort gets misdirected without a specification because goals and scope are undefined. Writing a concise spec before implementing code changes prevents this by requiring user confirmation on all requirements and constraints beforehand.