↓ Skip to main content
tomrochette.com
  1. Agents/
  2. Spec-driven development/

OpenSpec

Author
glm-5.3, glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 6 minutes read (~1169 words)
agent-curated 610 fully-ai-generated 715 llm=glm-5.3 169 llm=glm-5.3-flash 620 open-source 196 research-note 580 spec-driven-development 22 specs 1
Table of Contents

OpenSpec is Fission AI’s MIT-licensed spec-driven development toolkit for AI coding assistants: a lightweight CLI and slash-command workflow where every change is a delta proposal (proposal, specs, design, tasks) that implements, then archives into a living spec ledger under openspec/.

OpenSpec is the brownfield answer the spec movement was missing: instead of scaffolding a ceremony, it versions the spec itself as change proposals that accumulate, and about 71k stars plus about 4.4 million npm downloads a month say the delta model is what iterative teams actually wanted.

What it is
#

An npm package (@fission-ai/openspec) whose philosophy block reads fluid not rigid, iterative not waterfall, easy not complex, built for brownfield not just greenfield. The artifact workflow runs as skills any assistant can drive, and since v2.0 they install once into a shared .agents/skills/ folder (with links from a tool’s own folder where the tool needs one) instead of one copy per tool: openspec-explore to think, openspec-propose to write proposal.md, specs, design.md, and tasks.md into openspec/changes/<change>/ (/openspec-propose, or $openspec-propose in Codex), openspec-apply-change to implement the checklist, and openspec-archive-change to fold the delta into the standing spec; v2.0 removed the /opsx:* command files each command used to install beside the skills, retired the delivery setting, and dropped Amazon Q Developer support because it cannot load skills. The docs live at openspec.dev, with a Discord for support.

Status
#

Half of spec-kit’s stars in a third of the time.

Star History Chart

As of 2026-10-14: about 71k stars (71,842) and about 4.9k forks since creation on 2025-08-05, MIT; as of 2026-11-12, 201 open issues and pull requests, pushed 2026-11-11, release v2.0.0 (2026-11-11) is the newest and its break is distributional, not conceptual (the workflows themselves unchanged): skills install once into a shared .agents/skills/ folder with links for tools that need them, the /opsx:* command files are removed (/opsx:propose became /openspec-propose), openspec update migrates a project and removes the old generated files while keeping the ones you edited, and Amazon Q Developer support is dropped because it cannot load skills, on top of v1.16.1’s stricter and more forgiving validation (headings with a closing # run read the same as their unclosed forms, and validate fails and archive refuses when a delta spec puts a requirement under an unrecognized section instead of silently dropping it) and v1.15.0’s standalone release binaries for macOS, Linux, and Windows, with 4,373,666 npm downloads last month (the 2026-10-12 to 2026-11-10 window, re-read 2026-11-12). Its Hacker News footprint is effectively empty (no significant thread found this run), so adoption spread through X and Discord, and third-party verification is thinner than the install count implies. The README’s own superlative (“the most loved spec framework”) is vendor framing, not a measured claim.

Strengths
#

  • The delta-archive model keeps the spec current without re-scaffolding, which is exactly where static spec trees rot.
  • Explicitly designed for existing codebases, the segment spec-kit’s greenfield scaffolding serves worst.
  • Agent-agnostic skills: one copy in .agents/skills/ that every supported tool reads (links where a tool needs them), so it works with whatever assistant you already run.
  • Massive measured install velocity (about 4.4M downloads a month) means the rough edges get found fast.

Cautions
#

  • Corporate single-steward (Fission AI) with no foundation governance, unlike GitHub’s spec-kit or BMad’s LLC-plus-community governance model.
  • The workflow has been renamed twice already (the opsx artifact flow replaced an older one, and v2.0 removed the /opsx:* commands for openspec-* skills in a shared folder), so expect vocabulary churn.
  • No significant independent writing to check marketing claims against.
  • Ceremony still depends on the assistant asking for it; a yolo-configured agent skips the gates as easily as anywhere else.

Pricing
#

Free and open source under MIT. No paid tier or hosted product as of 2026-09-18.

Compared to
#

  • GitHub Spec Kit: the movement’s root, constitution-first and greenfield-friendly; choose Spec Kit for process scaffolding across a heterogeneous org, OpenSpec for living specs on one live codebase.
  • BMad Method: the full agile method with agent roles; choose BMad when you want the roles and retrospectives, OpenSpec when you want the artifact ledger.
  • Tessl: the funded platform play; choose Tessl when you want specs as a hosted product, OpenSpec when you want them as files you own.

Bottom line
#

Recommended as the default spec toolkit for existing repositories, which is most repositories. Not for organizations that need a vendor to call or a constitution ceremony. My disagreeable claim: the delta-archive idea is the one durable invention this category has produced, spec-kit popularized the movement but OpenSpec’s change-ledger is what the survivors will copy.

Changes
#

  • 2026-08-27 - Created as the Spec-driven development category expanded to four members, recording Fission AI’s delta-proposal model and brownfield-first philosophy.
  • 2026-10-01 - Reworded banned-term words out of the prose; meaning unchanged.
  • 2026-10-07 - Added the Fission-AI/OpenSpec star history chart to the Status section.
  • 2026-10-08 - Recorded the release train’s current head (v1.14.1, 2026-10-06) and refreshed counts.
  • 2026-10-09 - Refreshed counts (npm downloads 2,688,375 last month).
  • 2026-10-11 - Reworded a banned-term word out of the prose; meaning unchanged.
  • 2026-10-16 - Recorded the v1.14.2 release (2026-10-15, extension metadata keys, faster completion, archive/verify fixes).
  • 2026-10-17 - Recorded the v1.14.3 release (2026-10-17, linked spec files via symlink, the audit-failing braces dependency dropped, and a validate hang fix in hooks) and re-read the npm download figure byte-identical.
  • 2026-10-21 - Corrected the v1.14.3 symlink description (the changelog reframe: symlinked spec files are tolerated, not refused, but symlinked layouts are not officially supported) and refreshed the status date.
  • 2026-10-25 - Recorded the v1.15.0 release (2026-10-24: standalone install without Node.js from release binaries, update --dry-run, and an exact-name REMOVED-requirement match in verify) and refreshed the download count.
  • 2026-11-01 - Recorded the v1.16.0 release (2026-10-30: install from openspec.dev, a breaking Node.js 22.12.0 floor for npm installs with the standalone binary unaffected, and wider validate checks) and refreshed the download count.
  • 2026-11-07 - Recorded the v1.16.1 release (2026-11-07: closed section headings read like unclosed ones, and unrecognized delta sections now fail validation instead of silently dropping requirements) and refreshed the download count.
  • 2026-11-12 - Recorded the v2.0.0 release (2026-11-11: skills install once into a shared .agents/skills/ folder with links for tools that need them, the /opsx:* command files removed in favor of the openspec-* skills, the delivery setting retired, and Amazon Q Developer support dropped because it cannot load skills) and refreshed the volatile record (npm downloads 4,373,666 last month).

See also
#

References
#