Update SpecBind¶

Updating SpecBind has two separate parts: updating the specbind executable on your machine and refreshing the product-managed files installed in each project.

This guide uses mise as the primary binary manager. SpecBind does not provide a self-update command that replaces its own executable.

1. Update the binary with mise¶

From the project root, upgrade to the newest version allowed by the configured version selector:

mise upgrade github:Huruikagi/specbind
specbind --version

When mise.toml selects latest, mise chooses the newest stable release that satisfies its minimum_release_age setting. An exactly pinned version does not advance through an ordinary mise upgrade. Select an exact target explicitly when you intend to change that pin:

mise use github:Huruikagi/specbind@<version>
specbind --version

If mise.toml or mise.lock changed, review both files and commit them through the project's normal workflow. mise.lock keeps the selected version and distribution inputs reproducible for the team and CI. See mise's upgrade and mise.lock documentation for the installation client's exact behavior.

Commit before refreshing project assets

When the next specbind install plan replaces, moves, or removes existing files, SpecBind requires a repository with at least one commit and a clean worktree. If mise changed mise.toml or mise.lock, commit that change before continuing.

2. Refresh product-managed project files¶

The new binary embeds the Skills and other product-managed assets for that version. Inspect the project refresh plan first:

git status --short
specbind install --dry-run

Review the reported create, replace, and keep actions, plus any remove actions for retired product-managed targets. Then apply the plan:

specbind install
git status --short
git diff

Review and commit the resulting project changes through the normal workflow. Other team members who pull the updated project can run mise install to get the binary pinned by the lockfile. They receive the refreshed project files through Git and do not all need to rerun specbind install.

What changes and what is retained¶

Target	Owner	Update behavior
`specbind` executable	mise	Updated by `mise upgrade` or an explicit `mise use`
Product-managed targets such as `.agents/skills/sb-` and `.claude/skills/sb-`	SpecBind	Replaced with the current embedded versions by `specbind install`; retired targets are shown and removed through the plan
SpecBind-managed block in `AGENTS.md` or `CLAUDE.md`	SpecBind	Only the marked block is maintained; surrounding text is preserved
Templates, Rules, and Adapters below `.specbind/settings/`	Project	Existing files are never overwritten; newly introduced missing defaults may be created
Specs, Roadmap, Gates, and release history	Project	Not changed by `specbind install`

Direct edits to product-managed Skills are not a supported customization surface. If a refresh finds dirty managed targets, SpecBind stops instead of guessing or overwriting them. Move the needed policy to a project-owned surface or restore the managed target through Git before planning again.

If mise did not install the binary¶

Update the binary by rerunning the same installer used to place it. See Install the CLI in the README for the available installers and supported environments. After updating the binary, the specbind install --dry-run and specbind install project-refresh steps are the same as the mise flow.

User guide | Install SpecBind | Remove an Agent or uninstall