
OpenSpec
Plain-text specs that your AI coding assistant and you agree on before any code is written.
- Stars
- 73.7k
- Forks
- 5k
- Licence
- MIT
- Language
- TypeScript
- Last update
- 4 days ago
- Type
- Dev tool
What it is
OpenSpec is a command-line tool that adds a lightweight specification layer to AI coding assistants. Before the assistant writes code, you and the AI create a proposal, requirement specs, a design, and a task list in an openspec/ folder inside your project. You review that plan, then the AI implements it and archives the change when done.
- Turn a rough idea into a proposal, specs, design and tasks with /opsx:explore and /opsx:propose
- Have an AI apply a checklist of implementation tasks step by step with /opsx:apply
- Archive a finished change so its specs update the project's current specs with /opsx:archive
- Keep requirements as readable Markdown files with concrete WHEN/THEN scenarios in the repo
Great for
- Developers who use AI coding assistants and want to agree on requirements before code is written
- Teams working on existing (brownfield) codebases, which the README names as a design goal
- Solo developers who want their AI to stay on a defined plan within one repo
- Teams that want to share specs across several repositories (Stores, in beta)
Not ideal for
- People who want a rigid, phase-gated process: the README positions OpenSpec as fluid and iterative, not waterfall
- Projects that do not use an AI coding assistant, since the workflow is built around slash commands in those tools
- Anyone needing a stable cross-repo feature, because Stores are described as beta
How to get it
- 1
Install with a package manager
You'll need: Node.js 20.19.0 or higher (only if using the npm install route) · On Alpine Linux: libstdc++ and libgcc packages for the binary install
Install with npm (requires Node.js 20.19.0+)
npm install -g @fission-ai/openspec@latestInstall with Homebrew
brew install openspecInitialize in your project
cd your-project && openspec init - 2
Run it
- Install the CLI using one of the methods in the README
- Run openspec init inside your project directory
- In your AI assistant, run /opsx:explore if you are unsure what to build, or /opsx:propose <name> if you know
- Review the generated proposal, specs, design and tasks, then run /opsx:apply
- 3
Get the most out of it
- Use /opsx:explore first to shape a plan before proposing code changes
- Select the expanded workflow with openspec config profile, then apply it with openspec update, to get commands like /opsx:verify and /opsx:bulk-archive
- Read the project customization docs for profiles, project config and schemas
- Check the community schemas catalog for third-party workflow bundles
Downloads
Strengths
- Plain Markdown specs with no special syntax to learn
- Works with 30+ AI assistants via slash commands, according to the README
- Ships as a single binary install that the README says needs no Node.js
Trade-offs
- Stores, the cross-repo feature, are labeled beta in the README
- Slash command names vary by tool (for example /opsx-propose in Cursor and GitHub Copilot), which adds some setup confusion
- Value depends on your AI assistant following the spec files reliably, which the README does not measure
How it compares
| Project | Stars | Type | Level | Updated | Best for |
|---|---|---|---|---|---|
| OpenSpec (this) | 73.7k | Dev tool | beginner | 4 days ago | Developers who use AI coding assistants and want to agree on requirements before code is written |
| spec-kit | 145k | Dev tool | intermediate | 6 days ago | Developers who use an AI coding agent and want more predictable results from it |
| get-shit-done | 64.2k | Dev tool | intermediate | 5 months ago | Developers who already use Claude Code and want to find the current GSD project |
| planning-with-files | 27.8k | Dev tool | beginner | 6 days ago | Developers running long multi-step tasks in Claude Code or Codex CLI |
| gsd-core | 11.1k | Framework | intermediate | 4 days ago | Developers already using Claude Code, Codex, Cursor, or another supported AI coding runtime |
| Trail-Code | 11k | Dev tool | beginner | 4 days ago | Developers who use Claude Code, Cursor, Codex or similar agents on a medium or large repository |
Stats synced from GitHub. The assessment above was drafted with AI from the project's README on 2026-10-29 and may miss recent changes — check the README before relying on a command. MIT licence: free to use, modify and distribute, including commercially, as long as you keep the copyright notice.