skills.rest
insightriot
insightriotOFFICIAL
Explore all skills by this author →
GitHub

spec-driven-development

Creates structured specifications before coding through a gated four-phase workflow.

1|Updated Apr 13, 2026
Search Tags:#workflow#planning#documentation#software design#specification#requirements#acceptance criteria
One-click install
npx skills add https://github.com/insightriot/signal --skill spec-driven-development-insightriot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/insightriot/signal/tree/main/plugin/skills/define/spec-driven-development
Command: npx skills add https://github.com/insightriot/signal --skill spec-driven-development-insightriot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting to code with vague or ambiguous requirements leads to rework, wrong assumptions, and features nobody asked for. This Skill forces a written specification before any code, surfacing hidden assumptions and defining testable success criteria up front. ## Core Features & Use Cases - Gated Four-Phase Workflow: Progresses through Specify, Plan, Tasks, and Implement phases, each requiring human review before advancing. - Six-Area Spec Template: Covers objective, commands, project structure, code style, testing strategy, and Always/Ask-First/Never boundaries. - Assumption Surfacing & Reframing: Lists assumptions explicitly and converts vague requests like "make it faster" into measurable success criteria. - Use Case: When asked to build a new dashboard feature with unclear requirements, use this Skill to write a spec with concrete acceptance criteria, get human approval, break it into verifiable tasks, and only then implement. ## Quick Start Ask the AI 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?▼

Write a spec covering six areas: objective, commands, project structure, code style, testing strategy, and boundaries. List your assumptions explicitly, get human review and approval, then break the spec into a plan and discrete tasks before implementing.

How to handle vague requirements like make it faster?▼

Reframe vague requirements as concrete success criteria, such as LCP under 2.5 seconds or data load under 500ms. Present these reframed targets to the human for confirmation before proceeding with implementation.

When should I not use spec-driven development?▼

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

What are the phases of spec-driven development?▼

The workflow has four gated phases: Specify, Plan, Tasks, and Implement. Each phase requires human review before advancing, ensuring misunderstandings are caught before code is written.

How do I keep a specification up to date?▼

Treat the spec as a living document: update it when decisions or scope change, commit it to version control alongside the code, and reference spec sections in pull requests that implement them.

Related Skills

Explore More Software Engineering Skills→
The-Vibe-CompanyThe-Vibe-Company
2.4k

to-spec

Synthesizes conversation context into a structured spec published to the project issue tracker.

Official
Intermediate
EtroxTaranEtroxTaran

implement-task

Implement development tasks by writing failing tests before minimal code.

Community
Intermediate
koolerkxkoolerkx

context-engineering

Load and organize project rules and specs into a context hierarchy.

Community
Advanced
tmchowtmchow
22

iterative:spike

Scope uncertain questions and build throwaway artifacts to validate ideas.

Community
Advanced