OpenSpec

Spec-driven development for coding assistants

Review the plan.
Not the pull request.

Your assistant writes the proposal, the requirements and the task list first. You read four short files before a line of code exists.

npm install -g @fission-ai/openspec@latest

openspec/changes/add-dark-mode/

Example from the project
proposal.md
Why, and what changesThe argument before the implementation.
specs/
Requirements and scenariosPlain Markdown, no syntax to learn.
design.md
Technical approachHow it will be built.
tasks.md
Implementation checklistWhat gets ticked off, one item at a time.

Four files a person can read in a few minutes. The project's own framing: your AI writes these, you review the plan before any code is written.
OpenSpec is built with OpenSpec, so its specs and in-flight changes are in the repository.

explore
Work out the approachBefore naming it a change.
propose
Write the four filesThe plan you actually review.
apply
Implement the tasksChecklist, not vibes.
archive
Fold it into the specsReady for the next feature.

Stated philosophy

Built for brownfield, not just greenfield. The project describes itself as fluid rather than rigid, iterative rather than waterfall, and scalable from personal projects to enterprises.