spec-driven-development

Transform ambiguous change requests into structured, testable specifications with acceptance criteria.

Updated Jun 18, 2026

Search Tags:#workflow #planning #software development #specification #requirements #acceptance criteria

Ready to run

npx skills add https://github.com/MinhDuyDEV/mdpi --skill spec-driven-development-minhduydev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/MinhDuyDEV/mdpi/tree/main/.pi/skills/spec-driven-development
Command: npx skills add https://github.com/MinhDuyDEV/mdpi --skill spec-driven-development-minhduydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams avoid costly rework by transforming ambiguous feature requests into precise, testable specifications before implementation begins.

Core Features & Use Cases

Requirement Clarification: Converts broad requests into defined goals, observable outcomes, constraints, and non-goals.
Specification Workflow: Guides work through gated phases covering vocabulary, planning, task breakdown, implementation, and verification.
Use Case: When a product team requests a complex feature, use this Skill to create an approved specification with acceptance criteria before developers start coding.

Quick Start

Use the spec-driven-development skill to turn this feature request into a complete specification with goals, constraints, acceptance criteria, and open questions.

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 do I need it?▼

Specification-driven software development transforms ambiguous feature requests into testable specifications before implementation begins. You need it for new features, significant behavior changes, and multi-system work requiring acceptance criteria and shared terminology.

How do I turn vague software ideas into clear implementation specs?▼

To turn vague ideas into clear implementation specs, define the project vocabulary, observable outcomes, constraints, non-goals, affected surfaces, gated approvals, and verification strategies to create a structured, testable development workflow.

How do I write acceptance criteria and define non-goals for a feature request?▼

Write acceptance criteria and non-goals by guiding the feature request through gated specification phases covering vocabulary, planning, task breakdown, implementation, and verification to define observable outcomes and explicit constraints.

What is the best way to plan complex multi-system software changes?▼

The best way to plan complex multi-system software changes is to generate an approved specification with defined goals, constraints, and verification strategies before coding begins, ensuring shared terminology across teams.

When should I not use a specification workflow for software development?▼

You should not use a specification workflow for trivial changes that lack ambiguous requirements or complex multi-system interactions, as defining vocabulary, gated approvals, and observable outcomes adds unnecessary overhead.

Does the spec-driven-development skill work for new feature requests?▼

Yes, the spec-driven-development skill works for new feature requests by converting broad requests into defined goals, constraints, acceptance criteria, and open questions to prevent costly rework before implementation.