spec-driven-development
A gated spec-first workflow for turning vague product requests into reviewable implementation tasks.
30-Second Summary
This skill asks an agent to write and validate a specification before implementation.
It separates specify, plan, tasks, and implementation so hidden assumptions surface early.
Use it when a change is broad enough that coding first would turn product uncertainty into code churn.
1-Minute Read
What it is
A SKILL.md workflow for creating a spec, implementation plan, and task list before touching code. It is built around review gates so the human can correct assumptions before the agent commits to an approach.
When to use it
Use it for new projects, larger features, architecture choices, or requests that still contain open questions. It is less useful for small, unambiguous edits where the success criteria are already obvious.
How to test it first
Give the agent a vague feature request and ask it to apply this skill without writing code. Check whether it records assumptions, asks only necessary questions, and produces specific success criteria.
Watch out
The workflow can feel heavy if every tiny task gets a full spec. Keep the spec short for narrow changes and require approval only at the gates that actually reduce risk.