GITHUB / SPEC-KIT
Spec-driven development
Define what to build before building it

The spec stops
being scaffolding

Spec Kit is an open-source toolkit for building software with any AI coding agent. Its claim is a reversal: specifications become executable, directly generating working implementations rather than just guiding them.

For decades code was king and the spec was scaffolding you built and discarded once the real work began. Flip that and the document you were going to throw away becomes the thing under version control.

Read the toolkit github.com/github/spec-kit
Order of authorityIllustrative
Specificationthe source
What to build and why, written before anything is generated.
Generates
Planderived
The approach the agent will take, traceable back to a line in the spec.
Tasksderived
Work broken into pieces small enough to check one at a time.
Implementationderived
Code, which is now the output of the process instead of its origin.
Edit here ↑ the spec, not the code below it
Stage names are the design study. The README states that specifications become executable and directly generate working implementations rather than just guiding them.
Works with any AI coding agent
Bring your own agent Ready-to-use process Or bring your own process Extensions and presets Role-based bundles

The README describes a ready-to-use spec-driven process that you can replace with your own, extended through presets and bundles, and built to work with any AI coding agent rather than one vendor.

Executable

A spec that runs

Calling the spec executable is what makes it worth maintaining, because a document nobody runs goes stale in a week.

Agent-neutral

Any coding agent

Keeping the process separate from the agent means the artifact survives when you switch tools next quarter.

Organizational

Built for the whole team

Bundles and presets exist because a methodology only holds if the second engineer gets the same setup as the first.