Skip to content
Search
DevelopmentGlossary

Spec-Driven Development

In spec-driven development the written spec is the source of truth, instead of the chat history. GitHub's open-source Spec Kit describes the flow as defining what to build and why, then turning the specification into a plan, tasks and working code, with a project "constitution" of standing rules that you create once per project. Other tools follow similar steps under different names.

It answers the main weakness of vibe coding: nobody can check code against an intent that was never written down. A good spec names the user and the problem, describes the behavior in testable terms, says what is out of scope, and states how you'll know it's done. Break the plan into small tasks (prompt decomposition) so each one can be reviewed and tested on its own. Qurtoo's article on prompting parallel coding agents shows how task specs keep several agents from colliding.

Example

# Spec: Export invoices to CSV

## Who and why
Office managers need last month's invoices in a spreadsheet for the accountant.

## Behavior
- A button on the Invoices page exports the selected month as CSV.
- Columns: number, customer, issue date, due date, total, status.
- Totals use two decimal places and no currency symbol.

## Out of scope
- Other formats, scheduling, emailing the file.

## Done when
- A test exports a fixture month and matches a saved CSV byte for byte.
- The button is reachable by keyboard.

When to use it

  • Features that will be maintained after the first version
  • Work split across several agents or people
  • Any build where you need to show what was asked for and what was delivered

When not to use it

  • Throwaway prototypes, where a spec costs more than the code
  • Exploratory work where you don't know yet what you want