OpenSpec

What it does

• Change-first workflow: /opsx:explore to shape an idea, /opsx:propose to create openspec/changes/<name>/ (proposal, specs, design, tasks), /opsx:apply to implement, /opsx:archive to fold the delta back into specs
• Specs are plain Markdown requirements with WHEN/THEN scenarios — your AI writes them, you review before any code exists
• Works with 30+ AI tools via slash commands (spelled /opsx-propose in Cursor, @opsx-propose in Amazon Q, $openspec-propose in Codex)
• Stores (beta): keep specs in a repo of their own, shared across teams and repos via git — one source of truth every coding agent can read

When to use it

Teams that want spec discipline without Spec Kit's phase gates — brownfield repos included, per the project's own positioning. Sweet spot: features spanning multiple repos or teams (one store-owned spec, read-only consumers), and solo developers who keep losing the thread in chat history. The README recommends high-reasoning models (Codex 5.5 / Opus 4.7) for both planning and implementation.

Getting started

npm install -g @fission-ai/openspec@latest (or brew install openspec; Node.js 20.19.0+ required), then in your project:

openspec init

Later upgrades: the same npm line, plus openspec update inside each project to refresh agent instructions.

Things to know

Anonymous telemetry (command names and version only) is on by default; opt out with openspec config set telemetry.enabled false, OPENSPEC_TELEMETRY=0, or DO_NOT_TRACK=1 — it auto-disables in CI. The expanded command set (/opsx:new, /opsx:ff, /opsx:verify, ...) is opt-in via openspec config profile. Stores are beta. Context hygiene matters: the README suggests clearing context before implementation.