spec-driven-development

Draft a structured specification before coding with gated phases.

Updated May 26, 2026

Search Tags:#planning #documentation #specification #requirements #software-engineering #spec-driven-development #phase-gate

Ready to run

npx skills add https://github.com/koolerkx/vibe-react-2d-map-editor-yaml --skill spec-driven-development-koolerkx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/koolerkx/vibe-react-2d-map-editor-yaml/tree/main/.claude/skills/spec-driven-development
Command: npx skills add https://github.com/koolerkx/vibe-react-2d-map-editor-yaml --skill spec-driven-development-koolerkx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-driven development helps teams avoid ambiguity and scope creep by requiring a structured specification before coding, ensuring alignment between engineers and stakeholders.

Core Features & Use Cases

Define objectives and acceptance criteria before implementation
Gate work through SPECIFY, PLAN, TASKS, and IMPLEMENT phases
Maintain a living document that is updated as decisions evolve

Quick Start

Draft a complete spec outlining objectives, commands, structure, and testing before coding.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

What is spec-driven development and how does it prevent scope creep?▼

Spec-driven development is a structured approach requiring a complete specification before coding to ensure team alignment. By drafting objectives, project structure, and testing strategy upfront, it prevents ambiguity and scope creep throughout the software engineering process.

How do I draft a structured specification before coding begins?▼

Drafting a structured specification involves defining objectives, commands, project structure, code style, and testing strategy. This process ensures clear consensus among stakeholders and engineers before any implementation work starts on the project.

Can I update the specification document as project decisions change?▼

Yes, the specification functions as a living document that updates as decisions evolve. It maintains alignment between engineers and stakeholders by reflecting changes throughout the gated, phase-based implementation workflow.

What phases are used to gate work in a phase-based specification workflow?▼

The phase-based specification workflow gates work through SPECIFY, PLAN, TASKS, and IMPLEMENT phases. This enforces a structured progression from initial requirements alignment to actual coding, ensuring clear consensus at each stage.

Does spec-driven development work for an existing codebase or only new projects?▼

Spec-driven development works by defining objectives and acceptance criteria before implementation, which applies to both new and existing projects. The living document adapts as decisions change, maintaining alignment regardless of project maturity.

Why should my team use a living spec instead of directly writing code?▼

Using a living spec ensures clear consensus between engineers and stakeholders by defining boundaries and testing strategy upfront. It prevents ambiguity and scope creep by enforcing a gated process from specification to implementation.