skills.rest
Qiuyi-Hong
Qiuyi-HongCOMMUNITY
Explore all skills by this author →
GitHub

spec-driven-development

Creates structured specifications with gated review phases before writing any code.

Updated Sep 15, 2026
Search Tags:#workflow#planning#documentation#specification#requirements#prd#capability map
One-click install
npx skills add https://github.com/Qiuyi-Hong/addyosmani-skills --skill spec-driven-development-qiuyi-hong
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/Qiuyi-Hong/addyosmani-skills/tree/main/skills/spec-driven-development
Command: npx skills add https://github.com/Qiuyi-Hong/addyosmani-skills --skill spec-driven-development-qiuyi-hong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents wasted engineering effort caused by ambiguous requirements by forcing a written, human-approved specification before any code is written, surfacing hidden assumptions early. ## Core Features & Use Cases - Gated Four-Phase Workflow: Moves work through Specify, Plan, Tasks, and Implement phases, each requiring human review before advancing. - Capability Decomposition: Detects when one request bundles several independently testable capabilities and proposes a capability map with module ids, dependencies, and build order. - Spec Template & Boundaries: Provides a six-section spec template covering objective, commands, structure, code style, testing strategy, and Always/Ask First/Never boundaries. - Use Case: When asked to build a new billing feature with vague requirements, use this Skill to surface assumptions, draft a spec with testable success criteria, and get approval before implementation begins. ## Quick Start Ask the agent to write a specification for the new feature before writing any code, including success criteria and boundaries.

Frequently Asked Questions about spec-driven-development

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

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

Start by listing your assumptions explicitly, then draft a spec covering objective, commands, project structure, code style, testing strategy, and boundaries. Have a human review and approve it before any implementation begins.

What is spec-driven development in software engineering?▼

Spec-driven development is a workflow where a written specification serves as the shared source of truth before code is written. It progresses through gated phases: Specify, Plan, Tasks, and Implement, each requiring human review.

When should I skip writing a spec for a code change?▼

Skip the full spec for single-line fixes, typo corrections, or changes where requirements are unambiguous and self-contained. Even simple tasks benefit from a two-line spec with acceptance criteria.

How do I break a large feature into smaller modules?▼

Detect when one requirement bundles several independently testable capabilities, then propose a capability map with stable kebab-case module ids, one-way dependencies, and a build order. Write a separate spec per module in dependency order.

Does this workflow work with OpenSpec or other spec tools?▼

Yes, the workflow is format-agnostic. If a project already uses OpenSpec or another specification system, keep that tool's artifact format and storage conventions while this process owns clarification, content, and approval gates.

Related Skills

Explore More Software Engineering Skills→
PacificStudioPacificStudio
264

deep-interview

Clarify ambiguous software requests through a structured Socratic interview.

Official
Advanced
Kafil99Kafil99

task_decomposer

Decompose specifications into ordered atomic tasks with dependencies and acceptance criteria.

Community
Advanced
45black45black
1

fullstack-spec

Map feature requests into modular frontend, API, and backend specifications.

Community
Advanced
hungthinh04hungthinh04

spike

Validate build ideas with throwaway prototypes and feasibility verdicts.

Community
Advanced