Upgrade to 2.1
OpenSpec 2.1 supports global skills for coding agents. What changes, and what to do about it.
In short: OpenSpec can now install its skills globally, so every project on your machine uses the same ones. To upgrade, update the CLI and run openspec update in each repo. It asks one question, and nothing changes until you answer.
What’s changing
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.
Moving to Vercel’s installer gives OpenSpec native support for global skill installation. Your coding agent can use the same OpenSpec skills across projects.
What you’ll see
The next time you run 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.Nothing changes until you choose. In CI or from an agent there is no question: update refreshes the skills where they are.
Keep in this project
Press Enter. The skills stay in your repo.
- Commit
openspec/config.yaml. It 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 pulls, runs
openspec update, and answers Yes when it offers to set up skills on their machine.
In a script, run openspec init --tools <ids> in place of step 2. Upgrade everyone’s CLI before you switch a repo: earlier versions only know project skills.
If a script sets up your repos
In 2.0, openspec init --tools claude in a new repo wrote the skills into that repo. It now installs them globally. To keep them in your project repo, add --scope project:
openspec init --scope project --tools claudeBefore you update
- Edited a built-in skill? Update replaces the built-in skill folders. Save your edits first, along with any file you added inside one.
openspec update --dry-runshows what will change. - Git. Installing or refreshing skills needs Git and access to GitHub.
- Already ran
npx skills add? Keep that install and runopenspec update.
Coming from 1.x? Upgrade to 2.0 covers the rest.