Skip to content

v2.1.1 - Offline skill installs, safer archive

Latest

Choose a tag to compare

@openspec-release-bot openspec-release-bot released this 19 Nov 22:26
0c737dc

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:

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 specs

  • Archive won't half-finish. If the archive folder for a change already exists, the archive workflow now stops before it touches any main spec. Before, it could update your main specs and then fail, leaving them out of step with the archive.
  • New main specs come out formatted. When archive creates a main spec, it puts a blank line after ## Purpose, so the file passes Prettier and markdownlint without a reformat.
  • Retiring a capability reads wrapped lines correctly. A requirement line that wraps onto a line starting with <, like <args> are passed on to the script, used to be read as stray HTML and block the retirement. It's now read as part of the sentence.

Validate catches more, earlier

  • Frontmatter at the top of a delta spec is allowed. openspec validate --strict no longer fails on a delta spec that starts with a YAML frontmatter block.
  • Overlong edits are flagged before archive. When a MODIFIED requirement grows past the 500-character limit, validate --strict now warns you, so you can trim it while you're still working on the change.

Upgrade advice that fits your install

  • Homebrew and Nix users get the right update command. openspec version --check and openspec update used to tell every install to run npm install -g, and even offered to run it. A Homebrew install is now told to run brew upgrade openspec, and a Nix install is no longer told to use npm.

Full changelog: v2.1.0...v2.1.1