Spec-driven development means writing a plan before any code. You create a clear specification that tells what to build and why. A human engineer reviews it first. This stops mistakes before they happen.
The process has four steps. First you specify everything. Then you plan. Then you list tasks. Only then do you code. Each step needs a human review before moving forward. This makes sure everyone agrees.
You also write down your assumptions and boundaries. For example, you list what you will always do, what you need to ask about, and what you must never do. This keeps the project safe and clear.
Global
mkdir -p ~/.claude/skills/spec-driven-developmentProject
mkdir -p .claude/skills/spec-driven-developmentSource Repository
To Issuesmattpocock/skills
Break plans into independent vertical slice issues for faster teamwork
Persona Project Managergoogleworkspace/cli
Easily coordinate projects, track tasks, schedule meetings, and share documents
Persona Team Leadgoogleworkspace/cli
Lead your team with daily standups, task coordination, and clear communication
Github Issuesgithub/awesome-copilot
Create update and manage GitHub issues with simple commands
Breakdown Plangithub/awesome-copilot
Generate complete project plans with epics, stories, and automated tracking
Create Github Issues Feature From Implementation Plangithub/awesome-copilot
Turn implementation plans into clear GitHub issues phase by phase
Create Github Issue Feature From Specificationgithub/awesome-copilot
Transform specs into GitHub issues quickly with a consistent template
Structured Autonomy Plangithub/awesome-copilot
Turn a feature request into clear commits with a structured step by step plan