Spectra CLI 6.0.0

spectra version and spectra update now cover your whole stack, not just the agents installed in your project.

Specify CLI:     ✓ up to date (0.16.4)
Core agents:     ! needs updating (0.12.14 -> 0.16.4)
Spectra CLI:     ✓ up to date (6.0.0)
Spectra agents:  ✓ up to date (1.3.1)

  You can update by running: spectra update

spectra update then brings every out-of-date part current after a single confirmation, in the order Specify CLI → Core agents → Spectra CLI → Spectra agents. It continues through partial failures, and anything whose status it could not establish is reported as unknown and skipped rather than acted on with a guess.

If you have upgraded Spec Kit at some point but never re-run its integration upgrade, this release will tell you — that gap was previously invisible.

⚠️ Breaking: spectra cli version and spectra cli update are retired

Both are absorbed into the top-level commands. Running either prints a message naming its replacement and exits 2:

$ spectra cli version
✗ `spectra cli version` has been retired. Use `spectra version` instead.

spectra cli uninstall is unchanged — removing the command from your machine is still a distinct action from updating your stack.

Upgrading from 5.x — read this first

spectra cli update cannot carry you across this boundary. On 5.x that is the command you would reach for, and on 6.0.0 it no longer updates anything. Use either of these instead:

# from inside a Spec Kit project — updates your whole stack
spectra update

# or from anywhere, if you only want the command itself
uv tool install spectra-cli --from git+https://github.com/xavient/spectra --force

After upgrading, spectra --help shows a single row under Tool commands.

Notes

• spectra version requires a Spec Kit project with Spectra installed, because it reports on that project. To read just the command's own version from anywhere, run bare spectra — the banner carries a cli vX.Y.Z line and touches nothing.
• --no-update-check suppresses only the lookup of the latest Spectra CLI release. Every other check still runs.
• Offline or without specify on PATH, affected rows report unknown while still showing what is installed locally, and the command still exits 0. spectra update will say plainly that nothing could be checked rather than implying everything is current.

The extension channel is unaffected

This is a CLI release. The Spectra extension stays at 1.3.1 — no agent was added, changed, or removed, and the two channels are versioned independently. You do not need to update your agents because of this release.

---

What's Changed

• Rebrand the course handbook as SDD with SPECTRA by Ali Bahaloo (@alibahaloo) in https://github.com/xavient/spectra/pull/6
• Rename the one-pager to capability-brief and link it from the landing page by Ali Bahaloo (@alibahaloo) in https://github.com/xavient/spectra/pull/7
• Give the landing page and capability brief one shared header by Ali Bahaloo (@alibahaloo) in https://github.com/xavient/spectra/pull/8
• docs: security, policy & compliance section + section nav by Ali Bahaloo (@alibahaloo) in https://github.com/xavient/spectra/pull/9
• Unify spectra version and update across all four stack components by Ali Bahaloo (@alibahaloo) in https://github.com/xavient/spectra/pull/11

Full Changelog: 5.0.0...6.0.0