spec-driven-development

Transform ambiguous requirements into structured specifications with measurable success criteria.

2|Updated May 3, 2026
One-click install
npx skills add https://github.com/Rosetears520/aili-workflows --skill spec-driven-development-rosetears520
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/Rosetears520/aili-workflows/tree/main/skills/spec-driven-development
Command: npx skills add https://github.com/Rosetears520/aili-workflows --skill spec-driven-development-rosetears520

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents code from being written based on unclear or incomplete requirements by forcing a structured specification with measurable success criteria before implementation starts.

Core Features & Use Cases

  • Clarifying assumptions early: Surfaces assumptions and unresolved questions so misunderstandings are caught before any code is written.
  • Gated workflow from SPECIFY to IMPLEMENT: Keeps the process in phases (SPECIFY → PLAN → TASKS → IMPLEMENT) and requires human review before moving forward.
  • Translates vague goals into testable outcomes: Reframes requirements into concrete, verifiable success criteria aligned with testing strategy and boundaries.

Quick Start

Ask the AI to produce a complete spec for your project feature, including objective, commands, project structure, code style example, testing strategy, boundaries, success 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
How do I turn vague software requirements into testable acceptance criteria?

Spec-driven development transforms vague software requirements into structured, human-reviewable specifications with measurable success criteria. It reframes ambiguous goals into concrete, verifiable outcomes aligned with testing strategy and boundaries before implementation.

What is the best way to prevent premature coding on multi-module features?

To prevent premature coding on multi-module features, use a gated SPECIFY, PLAN, TASKS, and IMPLEMENT workflow. This enforces explicit assumptions, boundaries, and taskable acceptance criteria, requiring human review before advancing to coding.

How does a spec-first development workflow handle unresolved project assumptions?

Spec-first development surfaces assumptions and unresolved questions early in the specification phase. This catches misunderstandings and clarifies boundaries before any code is written, ensuring implementation relies on a structured specification.

When do I need to write a complete specification before starting software architecture work?

You need a complete specification for new projects, feature work, and architectural decisions where scope spans multiple files and requires significant effort. It provides objective, commands, project structure, code style, testing strategy, and open questions.

Can I use spec-driven development for small single-file code changes?

Spec-driven development is designed for multi-module scope and significant implementation effort. For small single-file changes, the gated SPECIFY to IMPLEMENT workflow and formal specification may be unnecessary overhead.