OpenSpec

OpenSpec is an open-source framework for spec-driven-development with AI coding assistants. Each change gets its own folder of Markdown files that the agent writes and you review before any code is written. Its README states the philosophy as fluid not rigid, iterative not waterfall, easy not complex, built for brownfield as well as greenfield, and scalable from personal projects to enterprises.

Repository snapshot (GitHub API, 2026-11-20)

ItemDetail
RepoFission-AI/OpenSpec, TypeScript, MIT
Created2025-08-05
Activitylast push 2026-11-19; latest release v2.1.1 (2026-11-19)
Size75,315 stars, 5,158 forks
Installinstall script from openspec.dev, npm install -g @fission-ai/openspec@latest (Node.js 22.20.0 or higher) or Homebrew (brew install openspec)

Workflow (README)

  1. openspec init in the project. It prints the right command form for the coding tools you pick; 30+ tools are listed as supported.
  2. The workflow runs as agent skills, invoked as /openspec-<name> in most tools and $openspec-<name> in Codex, or requested in plain words.
  3. Explore: /openspec-explore is a no-stakes thinking step that reads your code and weighs options before any plan exists.
  4. Propose: /openspec-propose add-dark-mode creates openspec/changes/add-dark-mode/ with four artefacts: proposal.md (why and what changes), specs/ (requirements and scenarios), design.md (technical approach) and tasks.md (implementation checklist).
  5. Apply: /openspec-apply-change works through the tasks.
  6. Archive: /openspec-archive-change moves the change to openspec/changes/archive/ with a date prefix and updates the specs.

The default profile holds explore, propose, apply and archive. An expanded profile (selected with openspec config profile, applied with openspec update) adds openspec-new-change, openspec-continue-change, openspec-ff-change, openspec-verify-change, openspec-bulk-archive-change and openspec-onboard. Projects coming from 1.x and its /opsx:* commands follow an “Upgrade to 2.0” guide.

Spec format

Plain Markdown. Requirements use “SHALL” statements with concrete scenarios in WHEN and THEN form, grouped under headings such as “ADDED Requirements”. The repository is built with OpenSpec, so its own openspec/specs and openspec/changes folders serve as live examples.

Other features

  • A dashboard (shown as a screenshot in the README).
  • Stores (beta): planning kept in a repository of its own, with the same openspec/ layout shared by git push. They support features that span several code repositories, shared requirements owned by a platform team, and planning before code exists.

Compared with other methods

See the table in tinyspec. OpenSpec is a four-artefact, per-change workflow with an archive step; speckit adds a constitution and fixed stages; gsd-core and bmad-method go further into agent orchestration and roles.

Sources