spec-driven-development

Generate a structured SPEC.md with success criteria before coding.

Updated Apr 15, 2026

Search Tags:#requirements #testing strategy #success criteria #spec #engineering workflow #handoff planning

Ready to run

npx skills add https://github.com/ToanPV90/dotfiles --skill spec-driven-development-toanpv90

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/ToanPV90/dotfiles/tree/main/claude/.claude/skills/spec-driven-development
Command: npx skills add https://github.com/ToanPV90/dotfiles --skill spec-driven-development-toanpv90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wasted engineering time and rework by forcing clear requirements before any implementation begins.

Core Features & Use Cases

Assumptions surfacing: Identifies and confirms key unknowns early to avoid building the wrong thing.
SPEC.md creation: Produces a structured specification including objective, tech stack, commands, success criteria, testing strategy, and boundaries.
Gatekeeping and handoff: Requires human review and then hands off to the planning phase via writing-plans, ensuring separation of responsibilities.
Use case: Starting a new feature where requirements are vague, stakeholders disagree, or success criteria are not yet measurable.

Quick Start

Tell the AI to “create a SPEC.md for a new feature, ask my clarifying questions first, then prepare me to hand off to writing-plans once the spec is approved.”

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

How do I create a software specification before coding to prevent rework?▼

To prevent wasted engineering time, you create a structured software specification before any implementation begins. This process surfaces key unknowns early and produces a SPEC.md containing objectives, success criteria, testing strategy, and boundaries.

What is the best way to define measurable success criteria for vague feature requirements?▼

Defining measurable success criteria for vague requirements involves generating a structured specification document. This document forces clear requirements by establishing boundaries and a testing strategy, ensuring stakeholders agree on measurable outcomes before implementation planning.

How do I surface project assumptions early in the engineering workflow?▼

You surface project assumptions early by generating a SPEC.md that explicitly identifies and confirms key unknowns. This structured specification forces stakeholders to resolve ambiguities and evolving decisions before any code is written.

Does spec-driven development require human approval before implementation planning?▼

Spec-driven development requires explicit human-gated approval before proceeding to implementation planning. This gatekeeping ensures a thorough review of the SPEC.md, maintaining a strict separation of responsibilities before handing off to the planning phase.

When do I need to write a SPEC.md for a new feature?▼

You need to write a SPEC.md when starting a new feature where requirements are vague, stakeholders disagree, or success criteria are not yet measurable. It transforms ambiguity into a testable plan before coding begins.

How do I hand off a specification to the planning phase?▼

You hand off a specification to the planning phase via writing-plans after securing explicit human-gated approval. This ensures the structured SPEC.md, including objectives and testing strategy, is reviewed before implementation planning begins.