github Fission-AI/OpenSpec v2.1.0
v2.1.0 - Global skills

one hour ago

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 project:

openspec update

In a repo that has its own OpenSpec skills, you'll see this choice:

Where should OpenSpec keep this project’s skills?

❯ Keep in this project   Keep the skills in this repo.
  Switch to global       Install the skills globally, for every project on this machine.

Keep in this project. Press Enter. The skills stay in your repo. Commit openspec/config.yaml, which records your choice so your teammates aren’t asked. Choose this if GitHub’s hosted Copilot agent reads the skills from the repo. You can switch later with openspec init --scope global.

Switch to global. We recommend this for most teams. The skills are installed globally on your machine, and the copies in the repo are removed. Commit the removed files. Each teammate then pulls, runs openspec update, and answers Yes when it offers to set up skills on their machine. Upgrade everyone’s CLI before you switch a repo: earlier versions only know project skills.

In CI or from an agent there is no question: update refreshes the skills where they are.

If a script sets up your repos, add --scope project to keep new repos' skills in the repo:

openspec init --scope project --tools claude

Note: openspec update replaces the built-in skill folders. If you edited a built-in skill or added a file inside one, save it first. openspec update --dry-run shows what will change.

An npm install needs Node 22.20.0 or newer. The standalone executable needs nothing. If you already ran npx skills add, keep that install and run openspec update.

See the upgrade guide for more details.

Fixes

  • The Windows executables are now labeled as OpenSpec, published by FISSION AI INC. Their file properties used to name the build tool, and an antivirus product removed openspec.exe as a threat. If the download disappears or won't run, the installer now says antivirus is the likely cause and shows the npm install command.

Full changelog: v2.0.0...v2.1.0

Don't miss a new OpenSpec release

NewReleases is sending notifications on new releases.