Skip to content
Back to search

openspec

Spec-driven development (SDD) for AI coding assistants.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/fission-ai/openspec with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/fission-ai/openspec'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/fission-ai-openspec/badge.svg)](/listings/fission-ai-openspec)

HTML

<a href="/listings/fission-ai-openspec"><img src="/api/listings/fission-ai-openspec/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

**Requires Node.js 20.19.0 or higher.** Homebrew installs it as a dependency.

Install OpenSpec globally:

npm install -g @fission-ai/openspec@latest

Or install the official [Homebrew formula](https://formulae.brew.sh/formula/openspec) on macOS or Linux:

brew install openspec

Then navigate to your project directory and initialize:

cd your-project
openspec init

> **Want your AI to do it?** Paste the [setup prompt](docs-lab/start/installation.md#install-with-your-ai-assistant) into your coding assistant — it installs the CLI, runs `openspec init`, and verifies the result.

Now talk to your AI:

- **Not sure what to build yet?** Start with `/opsx:explore`, a no-stakes thinking partner that reads your code, weighs options, and shapes a plan before any code gets written. ([Explore guide](docs/explore.md)) - **Already know what you want?** Go straight to `/opsx:propose <what-you-want-to-build>`.

Both are in the default profile. If you want the expanded workflow (`/opsx:new`, `/opsx:continue`, `/opsx:ff`, `/opsx:verify`, `/opsx:bulk-archive`, `/opsx:onboard`), select it with `openspec config profile` and apply with `openspec update`.

`/opsx:propose` is the canonical name; your tool may spell it `/opsx-propose` (Cursor, GitHub Copilot), `@opsx-propose` (Amazon Q) or `$openspec-propose` (Codex). `openspec init` prints the right form for the tools you picked — see [How To Invoke](docs/supported-tools.md#how-to-invoke).

> [!NOTE] > Not sure if your tool is supported? [View the full list](docs/supported-tools.md) – we support 30+ tools and growing. > > Also works with Homebrew, pnpm, yarn, bun, and Nix. [See installation options](docs-lab/start/installation.md).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 255 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <a href="https://github.com/Fission-AI/OpenSpec">
  3. <picture>
  4. <source srcset="assets/openspec_bg.png">
  5. <img src="assets/openspec_bg.png" alt="OpenSpec logo">
  6. </picture>
  7. </a>
  8. </p>
  9. <p align="center">
  10. <a href="https://github.com/Fission-AI/OpenSpec/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/Fission-AI/OpenSpec/actions/workflows/ci.yml/badge.svg" /></a>
  11. <a href="https://www.npmjs.com/package/@fission-ai/openspec"><img alt="npm version" src="https://img.shields.io/npm/v/@fission-ai/openspec?style=flat-square" /></a>
  12. <a href="./LICENSE"><img alt="License: MIT" src="https://img.shields.io/badge/License-MIT-blue.svg?style=flat-square" /></a>
  13. <a href="https://discord.gg/YctCnvvshC"><img alt="Discord" src="https://img.shields.io/discord/1411657095639601154?style=flat-square&logo=discord&logoColor=white&label=Discord&suffix=%20online" /></a>
  14. </p>
  15. <details>
  16. <summary><strong>The most loved spec framework.</strong></summary>
  17. [![Stars](https://img.shields.io/github/stars/Fission-AI/OpenSpec?style=flat-square&label=Stars)](https://github.com/Fission-AI/OpenSpec/stargazers)
  18. [![Downloads](https://img.shields.io/npm/dm/@fission-ai/openspec?style=flat-square&label=Downloads/mo)](https://www.npmjs.com/package/@fission-ai/openspec)
  19. [![Contributors](https://img.shields.io/github/contributors/Fission-AI/OpenSpec?style=flat-square&label=Contributors)](https://github.com/Fission-AI/OpenSpec/graphs/contributors)
  20. </details>
  21. <p></p>
  22. Our philosophy:
  23. ```text
  24. → fluid not rigid
  25. → iterative not waterfall
  26. → easy not complex
  27. → built for brownfield not just greenfield
  28. → scalable from personal projects to enterprises
  29. ```
  30. <p align="center">
  31. Follow <a href="https://x.com/0xTab">@0xTab on X</a> for updates · Join the <a href="https://discord.gg/YctCnvvshC">OpenSpec Discord</a> for help and questions.
  32. </p>
  33. <!-- TODO: Add GIF demo of /openspec-propose → /openspec-archive-change workflow -->
  34. ## See it in action
  35. ```text
  36. You: /openspec-explore
  37. AI: What would you like to explore?
  38. You: I want dark mode but I'm not sure how to do it cleanly.
  39. AI: Let me look at your styling setup...
  40. Cleanest path here: CSS variables + a small theme context,
  41. with system-preference detection. No new dependencies. Scope it?
  42. You: Yes, let's do it.
  43. You: /openspec-propose add-dark-mode
  44. AI: Created openspec/changes/add-dark-mode/
  45. ✓ proposal.md — why we're doing this, what's changing
  46. ✓ specs/ — requirements and scenarios
  47. ✓ design.md — technical approach
  48. ✓ tasks.md — implementation checklist
  49. Ready for implementation!
  50. You: /openspec-apply-change
  51. AI: Implementing tasks...
  52. ✓ 1.1 Add theme context provider
  53. ✓ 1.2 Create toggle component
  54. ✓ 2.1 Add CSS variables
  55. ✓ 2.2 Wire up localStorage
  56. All tasks complete!
  57. You: /openspec-archive-change
  58. AI: Archived to openspec/changes/archive/2025-01-23-add-dark-mode/
  59. Specs updated. Ready for the next feature.
  60. ```
  61. <details>
  62. <summary><strong>What do the specs actually look like?</strong></summary>
  63. Plain Markdown — requirements with concrete scenarios, no special syntax to learn. Here's what goes in the `specs/` folder created above:
  64. ```markdown
  65. ## ADDED Requirements
  66. ### Requirement: Theme selection
  67. The app SHALL let users switch between light and dark themes,
  68. defaulting to the system preference.
  69. #### Scenario: User toggles dark mode
  70. - **WHEN** the user clicks the theme toggle
  71. - **THEN** the app switches to dark mode and persists the choice
  72. ```
  73. Your AI writes these; you review the plan before any code is written.
  74. OpenSpec is built with OpenSpec — browse this repo's live [specs](openspec/specs) and in-flight [changes](openspec/changes) for real examples at scale.
  75. </details>
  76. <details>
  77. <summary><strong>OpenSpec Dashboard</strong></summary>
  78. <p align="center">
  79. <img src="assets/openspec_dashboard.png" alt="OpenSpec dashboard preview" width="90%">
  80. </p>
  81. </details>
  82. ## Why teams adopt OpenSpec
  83. Solo, OpenSpec keeps you and your AI honest on a single repo. On a team, the hard part moves: a feature spans the API server, the web app, and a shared library; requirements are owned by one team and consumed by others; planning starts before any code exists.
  84. **[Stores](https://openspec.dev/docs/stores)** are the answer — planning in a repo of its own. The same `openspec/` shape you already know (specs and changes), shared by `git push` like anything else. One source of truth your whole team and every coding agent can read, across every repo.
  85. - **Cross-repo features** — one change, one plan, even when the code lands in three repos.
  86. - **Shared requirements** — a platform team owns the specs; product teams reference them read-only, right where their coding agent can read them. No drifting wiki.
  87. - **Plan before code** — capture the plan in the store now; the code repos catch up later.
  88. > Stores are in **beta**. Start with the [Stores guide](https://openspec.dev/docs/stores).
  89. ## Quick Start
  90. Install OpenSpec. On macOS or Linux, in your terminal:
  91. ```bash
  92. curl -fsSL https://openspec.dev/cli/install.sh | sh
  93. ```
  94. On Windows, in PowerShell:
  95. ```powershell
  96. irm https://openspec.dev/cli/install.ps1 | iex
  97. ```
  98. Prefer a package manager? `npm install -g @fission-ai/openspec@latest` (needs Node.js 22.20.0 or higher) or the official [Homebrew formula](https://formulae.brew.sh/formula/openspec), `brew install openspec`.
  99. Then navigate to your project directory and initialize:
  100. ```bash
  101. cd your-project
  102. openspec init
  103. ```
  104. > **Want your AI to do it?** Paste the [setup prompt](https://openspec.dev/docs/installation#install-with-your-ai-assistant) into your coding assistant — it installs the CLI, runs `openspec init`, and verifies the result.
  105. Now talk to your AI:
  106. - **Not sure what to build yet?** Start with `/openspec-explore`, a no-stakes thinking partner that reads your code, weighs options, and shapes a plan before any code gets written. ([Quickstart](https://openspec.dev/docs/quickstart))
  107. - **Already know what you want?** Go straight to `/openspec-propose <what-you-want-to-build>`.
  108. Both are in the default profile. If you want the expanded workflow (`openspec-new-change`, `openspec-continue-change`, `openspec-ff-change`, `openspec-verify-change`, `openspec-bulk-archive-change`, `openspec-onboard`), select it with `openspec config profile` and apply with `openspec update`.
  109. These are skills. Most tools invoke them as `/openspec-propose` and Codex as `$openspec-propose`, or you can ask for the work in plain words. `openspec init` prints the right form for the tools you picked — see [Supported Tools](https://openspec.dev/docs/supported-tools). Coming from 1.x and its `/opsx:*` commands? See [Upgrade to 2.0](https://openspec.dev/docs/upgrade-to-2).
  110. > [!NOTE]
  111. > Not sure if your tool is supported? [View the full list](https://openspec.dev/docs/supported-tools) – we support 30+ tools and growing.
  112. >
  113. > Also works with npm, Homebrew, pnpm, yarn, bun, and Nix. [See installation options](https://openspec.dev/docs/installation).
  114. ## Docs
  115. Full documentation lives at **[openspec.dev/docs](https://openspec.dev/docs)**.
  116. → **[Quickstart](https://openspec.dev/docs/quickstart)**: your first change, start to finish<br>
  117. → **[Set up your project](https://openspec.dev/docs/setup)**: what `openspec init` installs<br>
  118. → **[CLI](https://openspec.dev/docs/cli)**: terminal reference<br>
  119. → **[Supported Tools](https://openspec.dev/docs/supported-tools)**: tool integrations & install paths<br>
  120. → **[Customize](https://openspec.dev/docs/customize)**: profiles, project config, and schemas<br>
  121. → **[Stores](https://openspec.dev/docs/stores)**: plan in a separate repo, shared across your team (beta)<br>
  122. → **[Community Showcase](docs/community.md)**: projects and resources built with and for OpenSpec
  123. ## Community schemas
  124. Third-party schema bundles distributed via standalone repositories — these provide opinionated workflows that integrate OpenSpec with other tools, similar to how [github/spec-kit's community extension catalog](https://github.com/github/spec-kit/tree/main/extensions) handles tool integrations.
  125. → **[Browse the catalog](docs/customization.md#community-schemas)** in the customization docs.
  126. ## Why OpenSpec?
  127. AI coding assistants are powerful but unpredictable when requirements live only in chat history. OpenSpec adds a lightweight spec layer so you agree on what to build before any code is written.
  128. - **Agree before you build** — human and AI align on specs before code gets written
  129. - **Stay organized** — each change gets its own folder with proposal, specs, design, and tasks
  130. - **Work fluidly** — update any artifact anytime, no rigid phase gates
  131. - **Use your tools** — works with 30+ AI assistants via skills
  132. ### How we compare
  133. **vs. [Spec Kit](https://github.com/github/spec-kit)** (GitHub) — Thorough but heavyweight. Rigid phase gates, lots of Markdown, Python setup. OpenSpec is lighter and lets you iterate freely.
  134. **vs. [Kiro](https://kiro.dev)** (AWS) — Powerful but you're locked into their IDE and limited to Claude models. OpenSpec works with the tools you already use.
  135. **vs. nothing** — AI coding without specs means vague prompts and unpredictable results. OpenSpec brings predictability without the ceremony.
  136. ## Updating OpenSpec
  137. **Upgrade the CLI**
  138. With the standalone install, run `openspec install`. If you installed with npm:
  139. ```bash
  140. npm install -g @fission-ai/openspec@latest
  141. ```
  142. If you installed OpenSpec with Homebrew:
  143. ```bash
  144. brew upgrade openspec
  145. ```
  146. **Refresh agent instructions**
  147. Run this once to refresh the skills installed on your machine. If your team keeps skills in Git, run it in each project that commits them.
  148. ```bash
  149. openspec update
  150. ```
  151. ## Usage Notes
  152. **Model selection**: OpenSpec works best with high-reasoning models. We recommend Codex 5.5 and Opus 4.7 for both planning and implementation.
  153. **Context hygiene**: OpenSpec benefits from a clean context window. Clear your context before starting implementation and maintain good context hygiene throughout your session.
  154. ## Contributing
  155. Every change starts as an issue. We discuss it there, and if we agree to pursue it, a maintainer implements the change or invites you to build it with us.
  156. → **[CONTRIBUTING.md](CONTRIBUTING.md)**: the full process, from first issue to merged PR
  157. ## Other
  158. <details>
  159. <summary><strong>Telemetry</strong></summary>
  160. OpenSpec collects anonymous usage stats.
  161. We collect only command names and version to understand usage patterns. No arguments, paths, content, or PII. Automatically disabled in CI.
  162. **Opt-out (any one is enough):**
  163. - `openspec config set telemetry.enabled false` (global config; unset means on)
  164. - `export OPENSPEC_TELEMETRY=0` or `export DO_NOT_TRACK=1` (env overrides config)
  165. </details>
  166. <details>
  167. <summary><strong>Maintainers & Advisors</strong></summary>
  168. See [MAINTAINERS.md](MAINTAINERS.md) for the list of core maintainers and advisors who help guide the project.
  169. </details>
  170. ## License
  171. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.