Wiki / concepts / wiki

Spec-driven development

Writing each change as a proposal, design, task list and formal specs before an agent writes the code, and keeping those documents in the repository so later changes are checked against them. The term suffers from semantic diffusion: it covers everything from one giant prompt to opinionated, tool-driven workflows like openspec.

For it: michael-carducci reports a consistent process, consistent results, and an agent that stops starting each session from scratch. Earlier decisions surface when a new change contradicts them, and a written plan lets the agent detour around a roadblock and get back on route. tim-berglund finds it keeps a hobby project from turning into a random walk through features. Michael admits having mistaken it for 1990s functional specifications, and Tim says the critical takes Tim has seen don't match the practice.

Against it: matt-pocock dismisses specs-to-code as "vibe coding by another name" and deletes PRDs after implementation so stale documents don't mislead later agents (report). OpenSpec takes the opposite view and keeps archived specs as the project's memory. Related: programming-as-theory-building, agent-skill-file.

Source: report

Linked from

Michael CarducciOpenSpecProgramming as theory buildingTim Berglund