Fission-AI/OpenSpecPublic

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

AI summary: A spec-driven development framework promoting fluid and iterative software specifications for AI coding assistants.

Stars
75.4K
+340 today
Forks
5.1K
Watchers
280
Open issues
149
Open PRs
59
Contributors
~149
Commits
1.1K
Branches
234

TypeScriptMITCreated Aug 5, 2025Last push todayLatest release v2.1.1+570 stars this week+2.7K this month

Quick answers

What is OpenSpec?
A spec-driven development framework promoting fluid and iterative software specifications for AI coding assistants.
What does OpenSpec do?
OpenSpec introduces an iterative spec-driven development methodology tailored for modern AI coding assistants. The framework replaces rigid waterfall planning with an artifact-guided workflow that remains fluid and easily adaptable throughout the software development lifecycle. By utilizing context engineering, the tool enables AI agents to better understand and act upon software design documents and product requirements. This approach scales seamlessly from small personal tools to large enterprise architectures, specifically accommodating brownfield projects rather than just greenfield deployments.
Who is OpenSpec for?
This framework is targeted at software architects, technical product managers, and developers utilizing AI coding assistants. It serves engineering teams that require structured, yet flexible, methodologies to guide complex software development.
How do I get started with OpenSpec?
/opsx:propose "your idea"
How popular is OpenSpec on GitHub?
Fission-AI/OpenSpec has 75,358 stars and 5,149 forks on GitHub, and gained 570 stars in the last 7 days.
What license does OpenSpec use?
Fission-AI/OpenSpec is released under the MIT license.

Star history

since Sep 18, 2026
020K40K60KSep 2026Oct 2026Oct 2026Nov 2026
75.4K stars as of Nov 21, 2026. Measured daily since Sep 18, 2026; GitHub no longer exposes earlier star timestamps.

Update history

4 recorded
  • Nov 21, 2026New release v2.1.1 (previously v1.17.0).
  • Nov 10, 2026New release v1.17.0 (previously v1.15.0).
  • Oct 27, 2026New release v1.15.0 (previously v1.14.1).
  • Oct 13, 2026New release v1.14.1 (previously v1.13.2).

Contribution activity

commits per day, last 52 weeks
NovDecJanFebMarAprMayJunJulAugSepOctNovMonWedFri2025-11-23: 0 commits2025-11-24: 0 commits2025-11-25: 1 commit2025-11-26: 0 commits2025-11-27: 0 commits2025-11-28: 1 commit2025-11-29: 0 commits2025-11-30: 0 commits2025-12-01: 0 commits2025-12-02: 0 commits2025-12-03: 0 commits2025-12-04: 0 commits2025-12-05: 0 commits2025-12-06: 0 commits2025-12-07: 0 commits2025-12-08: 0 commits2025-12-09: 0 commits2025-12-10: 0 commits2025-12-11: 0 commits2025-12-12: 2 commits2025-12-13: 0 commits2025-12-14: 0 commits2025-12-15: 0 commits2025-12-16: 0 commits2025-12-17: 0 commits2025-12-18: 0 commits2025-12-19: 1 commit2025-12-20: 3 commits2025-12-21: 1 commit2025-12-22: 4 commits2025-12-23: 7 commits2025-12-24: 0 commits2025-12-25: 3 commits2025-12-26: 2 commits2025-12-27: 0 commits2025-12-28: 2 commits2025-12-29: 1 commit2025-12-30: 2 commits2025-12-31: 1 commit2026-01-01: 0 commits2026-01-02: 0 commits2026-01-03: 0 commits2026-01-04: 0 commits2026-01-05: 5 commits2026-01-06: 5 commits2026-01-07: 3 commits2026-01-08: 0 commits2026-01-09: 7 commits2026-01-10: 10 commits2026-01-11: 1 commit2026-01-12: 0 commits2026-01-13: 10 commits2026-01-14: 2 commits2026-01-15: 0 commits2026-01-16: 1 commit2026-01-17: 0 commits2026-01-18: 2 commits2026-01-19: 14 commits2026-01-20: 10 commits2026-01-21: 4 commits2026-01-22: 7 commits2026-01-23: 2 commits2026-01-24: 0 commits2026-01-25: 5 commits2026-01-26: 7 commits2026-01-27: 2 commits2026-01-28: 0 commits2026-01-29: 1 commit2026-01-30: 13 commits2026-01-31: 2 commits2026-02-01: 1 commit2026-02-02: 2 commits2026-02-03: 0 commits2026-02-04: 0 commits2026-02-05: 0 commits2026-02-06: 1 commit2026-02-07: 0 commits2026-02-08: 0 commits2026-02-09: 0 commits2026-02-10: 0 commits2026-02-11: 0 commits2026-02-12: 0 commits2026-02-13: 0 commits2026-02-14: 0 commits2026-02-15: 1 commit2026-02-16: 2 commits2026-02-17: 0 commits2026-02-18: 1 commit2026-02-19: 1 commit2026-02-20: 0 commits2026-02-21: 3 commits2026-02-22: 1 commit2026-02-23: 3 commits2026-02-24: 0 commits2026-02-25: 0 commits2026-02-26: 1 commit2026-02-27: 3 commits2026-02-28: 0 commits2026-03-01: 0 commits2026-03-02: 0 commits2026-03-03: 0 commits2026-03-04: 0 commits2026-03-05: 0 commits2026-03-06: 0 commits2026-03-07: 0 commits2026-03-08: 0 commits2026-03-09: 0 commits2026-03-10: 0 commits2026-03-11: 0 commits2026-03-12: 0 commits2026-03-13: 0 commits2026-03-14: 0 commits2026-03-15: 0 commits2026-03-16: 0 commits2026-03-17: 0 commits2026-03-18: 0 commits2026-03-19: 0 commits2026-03-20: 0 commits2026-03-21: 0 commits2026-03-22: 0 commits2026-03-23: 0 commits2026-03-24: 0 commits2026-03-25: 0 commits2026-03-26: 0 commits2026-03-27: 0 commits2026-03-28: 0 commits2026-03-29: 0 commits2026-03-30: 0 commits2026-03-31: 0 commits2026-04-01: 0 commits2026-04-02: 0 commits2026-04-03: 0 commits2026-04-04: 1 commit2026-04-05: 0 commits2026-04-06: 0 commits2026-04-07: 0 commits2026-04-08: 0 commits2026-04-09: 5 commits2026-04-10: 1 commit2026-04-11: 2 commits2026-04-12: 8 commits2026-04-13: 2 commits2026-04-14: 2 commits2026-04-15: 1 commit2026-04-16: 0 commits2026-04-17: 0 commits2026-04-18: 0 commits2026-04-19: 0 commits2026-04-20: 1 commit2026-04-21: 2 commits2026-04-22: 2 commits2026-04-23: 0 commits2026-04-24: 0 commits2026-04-25: 0 commits2026-04-26: 0 commits2026-04-27: 0 commits2026-04-28: 0 commits2026-04-29: 0 commits2026-04-30: 3 commits2026-05-01: 1 commit2026-05-02: 5 commits2026-05-03: 0 commits2026-05-04: 2 commits2026-05-05: 1 commit2026-05-06: 6 commits2026-05-07: 1 commit2026-05-08: 0 commits2026-05-09: 0 commits2026-05-10: 0 commits2026-05-11: 0 commits2026-05-12: 0 commits2026-05-13: 0 commits2026-05-14: 0 commits2026-05-15: 1 commit2026-05-16: 0 commits2026-05-17: 0 commits2026-05-18: 0 commits2026-05-19: 0 commits2026-05-20: 0 commits2026-05-21: 1 commit2026-05-22: 0 commits2026-05-23: 2 commits2026-05-24: 0 commits2026-05-25: 0 commits2026-05-26: 0 commits2026-05-27: 1 commit2026-05-28: 1 commit2026-05-29: 2 commits2026-05-30: 0 commits2026-05-31: 1 commit2026-06-01: 3 commits2026-06-02: 2 commits2026-06-03: 2 commits2026-06-04: 0 commits2026-06-05: 0 commits2026-06-06: 0 commits2026-06-07: 0 commits2026-06-08: 0 commits2026-06-09: 0 commits2026-06-10: 0 commits2026-06-11: 0 commits2026-06-12: 0 commits2026-06-13: 0 commits2026-06-14: 0 commits2026-06-15: 0 commits2026-06-16: 0 commits2026-06-17: 0 commits2026-06-18: 0 commits2026-06-19: 0 commits2026-06-20: 0 commits2026-06-21: 0 commits2026-06-22: 0 commits2026-06-23: 0 commits2026-06-24: 6 commits2026-06-25: 0 commits2026-06-26: 0 commits2026-06-27: 0 commits2026-06-28: 2 commits2026-06-29: 0 commits2026-06-30: 0 commits2026-07-01: 0 commits2026-07-02: 0 commits2026-07-03: 2 commits2026-07-04: 0 commits2026-07-05: 0 commits2026-07-06: 1 commit2026-07-07: 4 commits2026-07-08: 7 commits2026-07-09: 1 commit2026-07-10: 2 commits2026-07-11: 2 commits2026-07-12: 0 commits2026-07-13: 0 commits2026-07-14: 0 commits2026-07-15: 0 commits2026-07-16: 0 commits2026-07-17: 16 commits2026-07-18: 6 commits2026-07-19: 6 commits2026-07-20: 7 commits2026-07-21: 1 commit2026-07-22: 23 commits2026-07-23: 7 commits2026-07-24: 0 commits2026-07-25: 0 commits2026-07-26: 0 commits2026-07-27: 13 commits2026-07-28: 10 commits2026-07-29: 4 commits2026-07-30: 2 commits2026-07-31: 1 commit2026-08-01: 0 commits2026-08-02: 0 commits2026-08-03: 0 commits2026-08-04: 14 commits2026-08-05: 13 commits2026-08-06: 0 commits2026-08-07: 1 commit2026-08-08: 0 commits2026-08-09: 0 commits2026-08-10: 0 commits2026-08-11: 20 commits2026-08-12: 3 commits2026-08-13: 1 commit2026-08-14: 0 commits2026-08-15: 0 commits2026-08-16: 0 commits2026-08-17: 0 commits2026-08-18: 0 commits2026-08-19: 18 commits2026-08-20: 0 commits2026-08-21: 1 commit2026-08-22: 0 commits2026-08-23: 0 commits2026-08-24: 1 commit2026-08-25: 0 commits2026-08-26: 11 commits2026-08-27: 0 commits2026-08-28: 0 commits2026-08-29: 0 commits2026-08-30: 0 commits2026-08-31: 0 commits2026-09-01: 1 commit2026-09-02: 18 commits2026-09-03: 1 commit2026-09-04: 0 commits2026-09-05: 0 commits2026-09-06: 0 commits2026-09-07: 0 commits2026-09-08: 0 commits2026-09-09: 15 commits2026-09-10: 0 commits2026-09-11: 0 commits2026-09-12: 0 commits2026-09-13: 0 commits2026-09-14: 0 commits2026-09-15: 0 commits2026-09-16: 35 commits2026-09-17: 4 commits2026-09-18: 0 commits2026-09-19: 0 commits2026-09-20: 0 commits2026-09-21: 0 commits2026-09-22: 20 commits2026-09-23: 11 commits2026-09-24: 0 commits2026-09-25: 1 commit2026-09-26: 0 commits2026-09-27: 0 commits2026-09-28: 1 commit2026-09-29: 36 commits2026-09-30: 5 commits2026-10-01: 3 commits2026-10-02: 2 commits2026-10-03: 0 commits2026-10-04: 0 commits2026-10-05: 7 commits2026-10-06: 1 commit2026-10-07: 0 commits2026-10-08: 0 commits2026-10-09: 0 commits2026-10-10: 0 commits2026-10-11: 0 commits2026-10-12: 0 commits2026-10-13: 0 commits2026-10-14: 19 commits2026-10-15: 1 commit2026-10-16: 0 commits2026-10-17: 6 commits2026-10-18: 0 commits2026-10-19: 0 commits2026-10-20: 2 commits2026-10-21: 0 commits2026-10-22: 7 commits2026-10-23: 2 commits2026-10-24: 3 commits2026-10-25: 0 commits2026-10-26: 0 commits2026-10-27: 0 commits2026-10-28: 0 commits2026-10-29: 0 commits2026-10-30: 18 commits2026-10-31: 0 commits2026-11-01: 0 commits2026-11-02: 1 commit2026-11-03: 0 commits2026-11-04: 1 commit2026-11-05: 0 commits2026-11-06: 5 commits2026-11-07: 1 commit2026-11-08: 0 commits2026-11-09: 5 commits2026-11-10: 2 commits2026-11-11: 4 commits2026-11-12: 0 commits2026-11-13: 1 commit2026-11-14: 0 commits2026-11-15: 0 commits2026-11-16: 3 commits2026-11-17: 3 commits2026-11-18: 6 commits2026-11-19: 4 commits2026-11-20: 0 commits2026-11-21: 0 commits
687 commits in the last yearLessMore

Signals and awards

derived from tracked data
  • Landmark project

    75,358 stars

  • Very active

    687 commits in 52 weeks

  • Community-driven

    ~149 contributors

  • Permissive license

    MIT

  • Continuous integration

    Automated checks passing

  • Repeat trending

    6 trending appearances

What OpenSpec does

OpenSpec introduces an iterative spec-driven development methodology tailored for modern AI coding assistants. The framework replaces rigid waterfall planning with an artifact-guided workflow that remains fluid and easily adaptable throughout the software development lifecycle. By utilizing context engineering, the tool enables AI agents to better understand and act upon software design documents and product requirements. This approach scales seamlessly from small personal tools to large enterprise architectures, specifically accommodating brownfield projects rather than just greenfield deployments.

This framework is targeted at software architects, technical product managers, and developers utilizing AI coding assistants. It serves engineering teams that require structured, yet flexible, methodologies to guide complex software development.

  • Iterative specification: Promotes fluid and adaptable software design documents rather than rigid waterfall planning.
  • AI assistant integration: Tailors product requirements and system architecture documents specifically for AI agents to process.
  • Artifact-guided workflow: Uses structured artifacts to direct the software development lifecycle effectively.
  • Brownfield support: Adapts seamlessly to existing legacy codebases rather than solely focusing on new greenfield projects.
  • Scalable architecture: Handles varying project complexities from individual developer tools to comprehensive enterprise systems.

Where teams use it

Guiding AI coding assistants

Write structured specifications that help AI agents understand the complete architecture before generating code.

Managing complex requirements

Maintain fluid product requirements that can evolve dynamically as project assumptions change.

Documenting brownfield architectures

Generate clear architectural specifications for existing legacy systems to assist new developers or AI tools.

Standardizing team planning

Implement a unified specification framework to streamline planning phases across large engineering teams.

Getting started: /opsx:propose "your idea"

README

main branch

OpenSpec logo

CI npm version License: MIT Discord

The most loved spec framework.

Stars Downloads Contributors

Our philosophy:
→ fluid not rigid
→ iterative not waterfall
→ easy not complex
→ built for brownfield not just greenfield
→ scalable from personal projects to enterprises

Follow @0xTab on X for updates · Join the OpenSpec Discord for help and questions.

See it in action

You: /openspec-explore
AI:  What would you like to explore?
You: I want dark mode but I'm not sure how to do it cleanly.
AI:  Let me look at your styling setup...
     Cleanest path here: CSS variables + a small theme context,
     with system-preference detection. No new dependencies. Scope it?
You: Yes, let's do it.

You: /openspec-propose add-dark-mode
AI:  Created openspec/changes/add-dark-mode/
     ✓ proposal.md — why we're doing this, what's changing
     ✓ specs/       — requirements and scenarios
     ✓ design.md    — technical approach
     ✓ tasks.md     — implementation checklist
     Ready for implementation!

You: /openspec-apply-change
AI:  Implementing tasks...
     ✓ 1.1 Add theme context provider
     ✓ 1.2 Create toggle component
     ✓ 2.1 Add CSS variables
     ✓ 2.2 Wire up localStorage
     All tasks complete!

You: /openspec-archive-change
AI:  Archived to openspec/changes/archive/2025-01-23-add-dark-mode/
     Specs updated. Ready for the next feature.
What do the specs actually look like?

Plain Markdown — requirements with concrete scenarios, no special syntax to learn. Here's what goes in the specs/ folder created above:

## ADDED Requirements

### Requirement: Theme selection
The app SHALL let users switch between light and dark themes,
defaulting to the system preference.

#### Scenario: User toggles dark mode
- **WHEN** the user clicks the theme toggle
- **THEN** the app switches to dark mode and persists the choice

Your AI writes these; you review the plan before any code is written.

OpenSpec is built with OpenSpec — browse this repo's live specs and in-flight changes for real examples at scale.

OpenSpec Dashboard

OpenSpec dashboard preview

Why teams adopt OpenSpec

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.

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.

  • Cross-repo features — one change, one plan, even when the code lands in three repos.
  • 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.
  • Plan before code — capture the plan in the store now; the code repos catch up later.

Stores are in beta. Start with the Stores guide.

Quick Start

Install OpenSpec. On macOS or Linux, in your terminal:

curl -fsSL https://openspec.dev/cli/install.sh | sh

On Windows, in PowerShell:

irm https://openspec.dev/cli/install.ps1 | iex

Prefer a package manager? npm install -g @fission-ai/openspec@latest (needs Node.js 22.20.0 or higher) or the official Homebrew formula, 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 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 /openspec-explore, a no-stakes thinking partner that reads your code, weighs options, and shapes a plan before any code gets written. (Quickstart)
  • Already know what you want? Go straight to /openspec-propose <what-you-want-to-build>.

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.

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. Coming from 1.x and its /opsx:* commands? See Upgrade to 2.0.

Note

Not sure if your tool is supported? View the full list – we support 30+ tools and growing.

Also works with npm, Homebrew, pnpm, yarn, bun, and Nix. See installation options.

Docs

Full documentation lives at openspec.dev/docs.

→ Quickstart: your first change, start to finish
→ Set up your project: what openspec init installs
→ CLI: terminal reference
→ Supported Tools: tool integrations & install paths
→ Customize: profiles, project config, and schemas
→ Stores: plan in a separate repo, shared across your team (beta)
→ Community Showcase: projects and resources built with and for OpenSpec

Community schemas

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 handles tool integrations.

→ Browse the catalog in the customization docs.

Why OpenSpec?

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.

  • Agree before you build — human and AI align on specs before code gets written
  • Stay organized — each change gets its own folder with proposal, specs, design, and tasks
  • Work fluidly — update any artifact anytime, no rigid phase gates
  • Use your tools — works with 30+ AI assistants via skills

How we compare

vs. Spec Kit (GitHub) — Thorough but heavyweight. Rigid phase gates, lots of Markdown, Python setup. OpenSpec is lighter and lets you iterate freely.

vs. Kiro (AWS) — Powerful but you're locked into their IDE and limited to Claude models. OpenSpec works with the tools you already use.

vs. nothing — AI coding without specs means vague prompts and unpredictable results. OpenSpec brings predictability without the ceremony.

Updating OpenSpec

Upgrade the CLI

With the standalone install, run openspec install. If you installed with npm:

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

If you installed OpenSpec with Homebrew:

brew upgrade openspec

Refresh agent instructions

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.

openspec update

Usage Notes

Model selection: OpenSpec works best with high-reasoning models. We recommend Codex 5.5 and Opus 4.7 for both planning and implementation.

Context hygiene: OpenSpec benefits from a clean context window. Clear your context before starting implementation and maintain good context hygiene throughout your session.

Contributing

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.

→ CONTRIBUTING.md: the full process, from first issue to merged PR

Other

Telemetry

OpenSpec collects anonymous usage stats.

We collect only command names and version to understand usage patterns. No arguments, paths, content, or PII. Automatically disabled in CI.

Opt-out (any one is enough):

  • openspec config set telemetry.enabled false (global config; unset means on)
  • export OPENSPEC_TELEMETRY=0 or export DO_NOT_TRACK=1 (env overrides config)
Maintainers & Advisors

See MAINTAINERS.md for the list of core maintainers and advisors who help guide the project.

License

MIT

View on GitHub

Recent activity

commits and pull requests

Releases and announcements

61 total
  1. v2.1.1 - Offline skill installs, safer archivev2.1.1Nov 19, 20262.6K downloads

    # OpenSpec 2.1.1 This release smooths out a handful of rough edges. Skills now install straight from the CLI, with no Git and no network needed. Archive is more careful with your main specs, and `validate --strict` catches two problems before they reach archive. Your workflows don't change. ## How to upgrade Update the OpenSpec CLI, then run this in each project: ```bash openspec update ``` ## Skills install from the CLI itself - **No more Git or GitHub needed to install skills.** In 2.1.0, `openspec init` and `openspec update` cloned the skills from GitHub, so they failed without Git, behind a strict firewall, or offline. The skills now come from the CLI package you already installed, so setup works anywhere and the skills always match your CLI version. - **`npx skills add` installs stay up to date.** If you added the OpenSpec skills to a project with `npx skills add`, `openspec update` used to skip them. It now finds them and refreshes them like any other install. - **The continue workflow hands off to apply again.** When planning is complete, the continue skill tells you the plan is ready to review and that you can ask your agent to apply it. ## Archive is safer with your

  2. v2.1.0 - Global skillsv2.1.0Nov 17, 20268.2K downloads

    # OpenSpec 2.1 OpenSpec now supports global skills for coding agents. Install the skills once and your agent can use them in every project on your machine. As more teams adopt Vercel’s `skills` installer, it’s becoming a common way to install skills across coding tools. OpenSpec is adopting it too, so we can spend less time maintaining installer code and more time improving the skills themselves. The OpenSpec workflows themselves haven't changed. ## What changed - **Skills can be installed globally.** Vercel’s installer handles the location for each supported agent, whether it reads `~/.agents/skills/` or uses its own folder. - **`openspec update` asks where a project's skills should live.** In a repo that has its own OpenSpec skills, you choose once between keeping them in the repo and switching to global. Nothing changes until you choose. - **`openspec init --tools <ids>` in a new repo installs globally.** In 2.0 it wrote the skills into the repo. Add `--scope project` to keep them there. - **Skills are installed by Vercel’s `skills` package.** Installing or refreshing them needs Git and access to GitHub. ## How to upgrade Update the OpenSpec CLI, then run this in each pro

  3. # OpenSpec 2.0 OpenSpec now installs skills in `.agents/skills/` instead of keeping a separate copy for each coding agent. Tools that don't read this folder, like Claude Code and Kiro, get links to the same skills. We're also removing the `/opsx:*` slash commands. Each command already has a matching skill, so there's no need to maintain both. The OpenSpec workflows themselves haven't changed. ## What changed - **Skills are installed in `.agents/skills/`.** Every tool uses the same skills, without duplicate files across folders. - **`/opsx:*` commands are removed.** For example, `/opsx:propose` becomes `/openspec-propose` (or `$openspec-propose` in Codex). You can also just ask your agent for the work. - **`openspec update` removes files generated by older versions.** This includes old slash commands and duplicate skills. Files you've changed in the old locations are kept and listed. - The `delivery` setting is no longer needed. Existing configs keep working. - Amazon Q Developer support is removed because it can't load skills. We recommend Kiro instead. ## How to upgrade Update the OpenSpec CLI, then run this in each project and commit the changes: ```bash openspec update `

  4. v1.17.0 - Safe upgrades, 2.0 noticev1.17.0Nov 9, 20265.8K downloads

    ## What's New in v1.17.0 `openspec update` now upgrades a project from any older release in one run, and announces that command files go away in OpenSpec 2.0. > **Heads-up: command files (`/opsx:*`) go away in OpenSpec 2.0.** Your OpenSpec skills stay and do the same work. To switch now, run `openspec config set delivery skills && openspec update`. The plan is in [#2022](https://github.com/Fission-AI/OpenSpec/issues/2022). ### New - **2.0 notice** - While a configured tool still gets command files, `openspec update` ends with a short notice that they go away in 2.0, plus the one command to switch early. It stays silent once you use skills only, and for tools without command files, such as Codex. ### Improved - **Upgrades from any release** - `openspec update` now upgrades a project made by any release since 0.12 in one run, without stopping to ask for `--force`. It removes old OpenSpec files nobody edited, including leftover copies that made some tools show every skill twice, and keeps any file you changed. - **Safer cleanup** - Cleanup never touches files outside your project, even when a folder inside it links somewhere else, and never removes anything when a tool fails to

  5. v1.16.1 - Spec parsing, version checksv1.16.1Nov 7, 20264.9K downloads

    ## What's New in v1.16.1 A patch release that makes spec validation stricter and more forgiving in the right places, and makes `openspec version --check` reliable. ### Fixed - **Closed section headings** - `validate`, `show`, `list`, `view` and `archive` now read headings with a closing `#` run (`## Purpose ##`, `## ADDED Requirements ##`) the same as their unclosed forms. - **Unrecognized delta sections** - `validate` now fails, and `archive` refuses, when a delta spec puts a requirement under an unrecognized section such as `## DEPRECATED Requirements`, instead of passing with a warning and silently dropping that requirement. - **Version check with telemetry off** - `openspec version --check` now checks for a newer version even when telemetry is off or it runs in CI. Only `OPENSPEC_NO_UPDATE_CHECK` skips it; the background check in `openspec update` still honors the telemetry opt-out and CI. - **Standalone update offers** - `openspec version --check` on the standalone binary now offers only a release whose files are attached on GitHub, the same one `openspec install` would install, rather than a version npm has before the installer can get it. **Full Changelog**: https://gith

Code frequency

additions and deletions
+32.4K-32.4KWeek of 2025-11-23: +24 linesWeek of 2025-11-23: -20 linesWeek of 2025-11-30: +0 linesWeek of 2025-11-30: -0 linesWeek of 2025-12-07: +5,173 linesWeek of 2025-12-07: -9 linesWeek of 2025-12-14: +980 linesWeek of 2025-12-14: -242 linesWeek of 2025-12-21: +7,041 linesWeek of 2025-12-21: -275 linesWeek of 2025-12-28: +5,187 linesWeek of 2025-12-28: -901 linesWeek of 2026-01-04: +15,388 linesWeek of 2026-01-04: -2,265 linesWeek of 2026-01-11: +3,586 linesWeek of 2026-01-11: -196 linesWeek of 2026-01-18: +20,797 linesWeek of 2026-01-18: -11,517 linesWeek of 2026-01-25: +9,139 linesWeek of 2026-01-25: -6,073 linesWeek of 2026-02-01: +25 linesWeek of 2026-02-01: -20 linesWeek of 2026-02-08: +0 linesWeek of 2026-02-08: -0 linesWeek of 2026-02-15: +23,676 linesWeek of 2026-02-15: -9,490 linesWeek of 2026-02-22: +912 linesWeek of 2026-02-22: -248 linesWeek of 2026-03-01: +0 linesWeek of 2026-03-01: -0 linesWeek of 2026-03-08: +0 linesWeek of 2026-03-08: -0 linesWeek of 2026-03-15: +0 linesWeek of 2026-03-15: -0 linesWeek of 2026-03-22: +0 linesWeek of 2026-03-22: -0 linesWeek of 2026-03-29: +7 linesWeek of 2026-03-29: -5 linesWeek of 2026-04-05: +641 linesWeek of 2026-04-05: -176 linesWeek of 2026-04-12: +4,393 linesWeek of 2026-04-12: -254 linesWeek of 2026-04-19: +349 linesWeek of 2026-04-19: -66 linesWeek of 2026-04-26: +3,889 linesWeek of 2026-04-26: -169 linesWeek of 2026-05-03: +9,333 linesWeek of 2026-05-03: -2,055 linesWeek of 2026-05-10: +4,705 linesWeek of 2026-05-10: -261 linesWeek of 2026-05-17: +80 linesWeek of 2026-05-17: -5 linesWeek of 2026-05-24: +23,905 linesWeek of 2026-05-24: -3,459 linesWeek of 2026-05-31: +494 linesWeek of 2026-05-31: -169 linesWeek of 2026-06-07: +0 linesWeek of 2026-06-07: -0 linesWeek of 2026-06-14: +0 linesWeek of 2026-06-14: -0 linesWeek of 2026-06-21: +32,420 linesWeek of 2026-06-21: -24,517 linesWeek of 2026-06-28: +7,754 linesWeek of 2026-06-28: -98 linesWeek of 2026-07-05: +4,092 linesWeek of 2026-07-05: -5,672 linesWeek of 2026-07-12: +6,765 linesWeek of 2026-07-12: -631 linesWeek of 2026-07-19: +9,489 linesWeek of 2026-07-19: -2,635 linesWeek of 2026-07-26: +13,252 linesWeek of 2026-07-26: -2,222 linesWeek of 2026-08-02: +15,512 linesWeek of 2026-08-02: -1,987 linesWeek of 2026-08-09: +4,283 linesWeek of 2026-08-09: -661 linesWeek of 2026-08-16: +9,507 linesWeek of 2026-08-16: -1,464 linesWeek of 2026-08-23: +5,641 linesWeek of 2026-08-23: -567 linesWeek of 2026-08-30: +3,790 linesWeek of 2026-08-30: -1,321 linesWeek of 2026-09-06: +3,927 linesWeek of 2026-09-06: -430 linesWeek of 2026-09-13: +16,023 linesWeek of 2026-09-13: -1,932 linesWeek of 2026-09-20: +4,841 linesWeek of 2026-09-20: -969 linesWeek of 2026-09-27: +9,100 linesWeek of 2026-09-27: -2,872 linesWeek of 2026-10-04: +508 linesWeek of 2026-10-04: -389 linesWeek of 2026-10-11: +4,153 linesWeek of 2026-10-11: -1,962 linesWeek of 2026-10-18: +5,720 linesWeek of 2026-10-18: -1,469 linesWeek of 2026-10-25: +10,707 linesWeek of 2026-10-25: -7,668 linesWeek of 2026-11-01: +1,354 linesWeek of 2026-11-01: -394 linesWeek of 2026-11-08: +20,183 linesWeek of 2026-11-08: -5,289 linesWeek of 2026-11-15: +6,141 linesWeek of 2026-11-15: -4,504 linesNov 23, 2025Nov 15, 2026
+334.9K lines added, -107.5K removed over the last year.

Commits per week

last 52 weeks
470Week of 2025-11-23: 2 commitsWeek of 2025-11-30: 0 commitsWeek of 2025-12-07: 2 commitsWeek of 2025-12-14: 4 commitsWeek of 2025-12-21: 17 commitsWeek of 2025-12-28: 6 commitsWeek of 2026-01-04: 30 commitsWeek of 2026-01-11: 14 commitsWeek of 2026-01-18: 39 commitsWeek of 2026-01-25: 30 commitsWeek of 2026-02-01: 4 commitsWeek of 2026-02-08: 0 commitsWeek of 2026-02-15: 8 commitsWeek of 2026-02-22: 8 commitsWeek of 2026-03-01: 0 commitsWeek of 2026-03-08: 0 commitsWeek of 2026-03-15: 0 commitsWeek of 2026-03-22: 0 commitsWeek of 2026-03-29: 1 commitsWeek of 2026-04-05: 8 commitsWeek of 2026-04-12: 13 commitsWeek of 2026-04-19: 5 commitsWeek of 2026-04-26: 9 commitsWeek of 2026-05-03: 10 commitsWeek of 2026-05-10: 1 commitsWeek of 2026-05-17: 3 commitsWeek of 2026-05-24: 4 commitsWeek of 2026-05-31: 8 commitsWeek of 2026-06-07: 0 commitsWeek of 2026-06-14: 0 commitsWeek of 2026-06-21: 6 commitsWeek of 2026-06-28: 4 commitsWeek of 2026-07-05: 17 commitsWeek of 2026-07-12: 22 commitsWeek of 2026-07-19: 44 commitsWeek of 2026-07-26: 30 commitsWeek of 2026-08-02: 28 commitsWeek of 2026-08-09: 24 commitsWeek of 2026-08-16: 19 commitsWeek of 2026-08-23: 12 commitsWeek of 2026-08-30: 20 commitsWeek of 2026-09-06: 15 commitsWeek of 2026-09-13: 39 commitsWeek of 2026-09-20: 32 commitsWeek of 2026-09-27: 47 commitsWeek of 2026-10-04: 8 commitsWeek of 2026-10-11: 26 commitsWeek of 2026-10-18: 14 commitsWeek of 2026-10-25: 18 commitsWeek of 2026-11-01: 8 commitsWeek of 2026-11-08: 12 commitsWeek of 2026-11-15: 16 commitsNov 23, 2025Nov 15, 2026
687 commits in the last 52 weeks.

When work happens

weekday and hour
SunMonTueWedThuFriSat036912151821Sun 0:00 — 1 commitsSun 1:00 — 10 commitsSun 2:00 — 3 commitsSun 3:00 — 3 commitsSun 4:00 — 11 commitsSun 5:00 — 4 commitsSun 6:00 — 0 commitsSun 7:00 — 1 commitsSun 8:00 — 0 commitsSun 9:00 — 1 commitsSun 10:00 — 1 commitsSun 11:00 — 1 commitsSun 12:00 — 0 commitsSun 13:00 — 5 commitsSun 14:00 — 2 commitsSun 15:00 — 2 commitsSun 16:00 — 4 commitsSun 17:00 — 2 commitsSun 18:00 — 1 commitsSun 19:00 — 2 commitsSun 20:00 — 0 commitsSun 21:00 — 0 commitsSun 22:00 — 1 commitsSun 23:00 — 7 commitsMon 0:00 — 7 commitsMon 1:00 — 2 commitsMon 2:00 — 4 commitsMon 3:00 — 0 commitsMon 4:00 — 1 commitsMon 5:00 — 1 commitsMon 6:00 — 0 commitsMon 7:00 — 0 commitsMon 8:00 — 1 commitsMon 9:00 — 2 commitsMon 10:00 — 1 commitsMon 11:00 — 2 commitsMon 12:00 — 2 commitsMon 13:00 — 1 commitsMon 14:00 — 3 commitsMon 15:00 — 11 commitsMon 16:00 — 5 commitsMon 17:00 — 5 commitsMon 18:00 — 11 commitsMon 19:00 — 12 commitsMon 20:00 — 2 commitsMon 21:00 — 8 commitsMon 22:00 — 16 commitsMon 23:00 — 11 commitsTue 0:00 — 11 commitsTue 1:00 — 1 commitsTue 2:00 — 2 commitsTue 3:00 — 1 commitsTue 4:00 — 1 commitsTue 5:00 — 1 commitsTue 6:00 — 1 commitsTue 7:00 — 5 commitsTue 8:00 — 2 commitsTue 9:00 — 3 commitsTue 10:00 — 3 commitsTue 11:00 — 9 commitsTue 12:00 — 8 commitsTue 13:00 — 4 commitsTue 14:00 — 8 commitsTue 15:00 — 15 commitsTue 16:00 — 16 commitsTue 17:00 — 31 commitsTue 18:00 — 39 commitsTue 19:00 — 7 commitsTue 20:00 — 15 commitsTue 21:00 — 13 commitsTue 22:00 — 16 commitsTue 23:00 — 13 commitsWed 0:00 — 9 commitsWed 1:00 — 5 commitsWed 2:00 — 5 commitsWed 3:00 — 5 commitsWed 4:00 — 0 commitsWed 5:00 — 0 commitsWed 6:00 — 2 commitsWed 7:00 — 2 commitsWed 8:00 — 8 commitsWed 9:00 — 7 commitsWed 10:00 — 14 commitsWed 11:00 — 3 commitsWed 12:00 — 4 commitsWed 13:00 — 5 commitsWed 14:00 — 10 commitsWed 15:00 — 34 commitsWed 16:00 — 30 commitsWed 17:00 — 12 commitsWed 18:00 — 16 commitsWed 19:00 — 34 commitsWed 20:00 — 29 commitsWed 21:00 — 23 commitsWed 22:00 — 23 commitsWed 23:00 — 27 commitsThu 0:00 — 15 commitsThu 1:00 — 6 commitsThu 2:00 — 4 commitsThu 3:00 — 0 commitsThu 4:00 — 2 commitsThu 5:00 — 2 commitsThu 6:00 — 3 commitsThu 7:00 — 0 commitsThu 8:00 — 0 commitsThu 9:00 — 2 commitsThu 10:00 — 1 commitsThu 11:00 — 2 commitsThu 12:00 — 4 commitsThu 13:00 — 1 commitsThu 14:00 — 5 commitsThu 15:00 — 5 commitsThu 16:00 — 6 commitsThu 17:00 — 11 commitsThu 18:00 — 5 commitsThu 19:00 — 0 commitsThu 20:00 — 5 commitsThu 21:00 — 13 commitsThu 22:00 — 4 commitsThu 23:00 — 1 commitsFri 0:00 — 3 commitsFri 1:00 — 2 commitsFri 2:00 — 6 commitsFri 3:00 — 2 commitsFri 4:00 — 4 commitsFri 5:00 — 2 commitsFri 6:00 — 0 commitsFri 7:00 — 0 commitsFri 8:00 — 1 commitsFri 9:00 — 3 commitsFri 10:00 — 2 commitsFri 11:00 — 4 commitsFri 12:00 — 7 commitsFri 13:00 — 2 commitsFri 14:00 — 5 commitsFri 15:00 — 3 commitsFri 16:00 — 10 commitsFri 17:00 — 14 commitsFri 18:00 — 3 commitsFri 19:00 — 10 commitsFri 20:00 — 6 commitsFri 21:00 — 5 commitsFri 22:00 — 12 commitsFri 23:00 — 13 commitsSat 0:00 — 16 commitsSat 1:00 — 8 commitsSat 2:00 — 6 commitsSat 3:00 — 2 commitsSat 4:00 — 5 commitsSat 5:00 — 1 commitsSat 6:00 — 0 commitsSat 7:00 — 0 commitsSat 8:00 — 0 commitsSat 9:00 — 2 commitsSat 10:00 — 0 commitsSat 11:00 — 4 commitsSat 12:00 — 2 commitsSat 13:00 — 0 commitsSat 14:00 — 2 commitsSat 15:00 — 2 commitsSat 16:00 — 5 commitsSat 17:00 — 2 commitsSat 18:00 — 5 commitsSat 19:00 — 3 commitsSat 20:00 — 4 commitsSat 21:00 — 4 commitsSat 22:00 — 1 commitsSat 23:00 — 9 commits
Commit volume by weekday and hour (UTC). Larger dots mean more commits.
DateListRankStars gained
Sep 26, 2026weekly#14+1,415
Sep 25, 2026weekly#14+1,415
Sep 24, 2026weekly#12+1,538
Sep 23, 2026weekly#14+1,558
Sep 19, 2026daily#7+298
Sep 18, 2026daily#7+298
  • morluto/rea

    Reverse engineer anything with agents, from app behavior down to native binaries.

    471.6K stars · TypeScript

  • freeCodeCamp/freeCodeCamp

    freeCodeCamp.org's open-source codebase and curriculum. Learn math, programming, and computer science for free.

    459.4K stars · TypeScript

  • openclaw/openclaw

    The AI that really does things. Any OS. Any Platform. The lobster way. 🦞

    394.9K stars · TypeScript

  • obra/superpowers

    An agentic skills framework & software development methodology that works.

    322.9K stars · Shell

  • NousResearch/hermes-agent

    The agent that grows with you

    265K stars · Python

  • anomalyco/opencode

    The open source coding agent.

    228.3K stars · TypeScript