spec-driven-development

Creates structured specifications and capability maps before writing any code.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/visdomtech/skills --skill spec-driven-development-visdomtech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/visdomtech/skills/tree/main/spec-driven-development
Command: npx skills add https://github.com/visdomtech/skills --skill spec-driven-development-visdomtech

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 Mapping: Decomposes a request bundling several independently testable capabilities into a module map with stable ids, dependency direction, and build order. - Spec Template with Boundaries: Produces specs covering objective, commands, project 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, get it approved, then break it into ordered tasks before implementing. ## Quick Start Ask the AI to write a specification for your new feature before any coding begins, including objectives, 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 software specification before coding?▼

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

What is spec-driven development?▼

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

When should I decompose a feature into a capability map?▼

Decompose when one requirement bundles several independently testable capabilities, such as identity, billing, and notifications. Create a small module table with stable kebab-case ids, one-way dependencies, and a build order before writing module specs.

When should I skip writing a spec?▼

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.

Can I use this workflow with OpenSpec or other spec tools?▼

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

How do I turn vague requirements into testable criteria?▼

Reframe vague instructions as concrete success criteria with measurable targets. For example, translate "make the dashboard faster" into LCP under 2.5s on 4G, data load under 500ms, and CLS under 0.1, then confirm the targets with the human.