OpenSpec
Agree on the spec before the code: a lightweight spec layer that keeps you and your AI coding assistant honest, from one repo to a whole team.
Project intro
OpenSpec adds a lightweight spec layer to AI coding: before any code is written, you and your coding assistant agree on what to build. Each change gets its own folder with a proposal, requirements, design notes and a task checklist, all in plain Markdown, so the plan survives after the chat scrolls away.
The workflow is four short steps. Explore first when you are not sure what to build, propose the change to write it down, apply it to build the tasks one by one, then archive it so the specs stay current. The skills work with more than 30 assistants — Claude Code, Codex and the rest — and install with one command, npm, or Homebrew.
Teams get Stores: planning lives in a repo of its own, shared by git push, so one change can span the API server, the web app and a shared library without drifting into a wiki. A platform team can own the requirements while product teams reference them read-only, right where their coding agent can read them.
It has 75,258 stars on GitHub with 5,156 forks, was created in August 2025 and was last pushed on 19 November 2026. It needs Node.js 22.20 or newer, is MIT licensed, and collects only anonymous usage stats, which you can switch off. Two honest limits: it works best with high-reasoning models, and Stores are still in beta.
Actions
Tech stack
Project info
- Project category
- Developer Tools
- Project status
- Online
- Collaboration intent
- None