You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Removed the experimental specx command-line tool. Its install scripts and updates have stopped; use the npm version, spxa, instead. cli_command: specx in .spectra.yaml is automatically treated as spxa.
Interface
You can now open a project by dragging a folder onto the Spectra window. On macOS, you can also drop it on the Spectra icon in the Dock.
When the folder isn't under Git yet, "Initialize Spectra" now offers a "Create a Git repository" option, checked by default.
Added "Reveal in Finder" ("Reveal in File Explorer" on Windows) to the right-click menu of project icons in the left sidebar.
Project icons can now be SVG files.
Canceling "Initialize Spectra" now closes the project that hasn't been initialized and removes it from "Recent Projects".
Replaced the "S" at the top of the left sidebar with the Spectra logo.
CLI
Added an npm version of the CLI: install it with npm install -g @kaochenlong/spxa, and the command is spxa. It doesn't need the desktop app and works on Linux too.
Added spectra rename <old-name> <new-name> to rename a change; its related records move along with it.
Added spectra coverage <change>, which lists whether each scenario has a corresponding test.
spectra task start and spectra task done now accept the task numbers written in tasks.md, such as 2.1.
spectra archive --preview and the desktop app's archive confirmation dialog now list the reasons an archive would be blocked when it runs.
spectra decisions now also lists Non-Goals, along with the contents of parked changes.
spectra analyze now flags mistakes in task dependencies in tasks.md, such as pointing to a task that doesn't exist or two tasks waiting on each other.
spectra validate --specs now warns about specs whose Purpose hasn't been written yet.
Running spectra status, spectra instructions, or spectra scope with the name of an archived change now explains that it has been archived and which directory its files are in.
When run without --tools, spectra init now explains that no coding agent files were generated this time and lists the agents you can specify.
SDD Skills
Before making suggestions or writing design decisions, /spectra-discuss and /spectra-propose now check past decisions and Non-Goals. If one of them would be overturned, they say so first and leave the decision to you.
After it finishes, /spectra-propose translates the English specs into the project's language. Click "Translation" in the "Specs" tab on the Changes page to switch to the translated version.
/spectra-apply checks off implementation tasks as soon as the code is done, and lists the items that need your own acceptance separately.
When requirements change partway through apply, the agent now updates the plan with /spectra-ingest instead of entering plan mode on its own and interrupting you.
/spectra-debug doesn't change files without your consent. After investigating, it reports the cause and a suggested fix, and lets you decide whether to fix it now, fold it into an existing change, or open a new change.
/spectra-verify now tells apart requirements that a change removes or renames, and doesn't treat them as unimplemented.
When fixing a problem, the agent fixes the root cause instead of settling for a quick patch that only treats the symptom because the real fix takes more work.
When /spectra-apply writes a test, it notes above the test which scenario it verifies, so you can check with spectra coverage.
With TDD on, tests verify actual behavior; tests that only check fixed copy or layout are no longer required.
With "Security Audit" on, /spectra-apply loads the full security checklist.
When a change is too large and gets split into several, the ones that must be done in order get a 01-, 02- prefix in their names.
When a coding agent can't find the spectra command (for example, because the agent was started before Spectra), it now runs it from the default install location and reminds you to fully quit the agent and start it again.
Fixes
Fixed the Windows installer showing "Error opening file for writing" when a terminal or coding agent was running spectra during an update, leaving the CLI on the old version.
Fixed spectra <folder> in a terminal sometimes not opening the project when the desktop app was already open.
Fixed reinitializing a project (spectra init --force or initializing from the desktop app) overwriting the entire config.yaml in the spec directory with the default content.
Fixed creating a change with the name of a parked change overwriting the parked one. It's now refused, with a hint to restore it with spectra unpark <name>.
Fixed "Base Font Size" in Settings having no effect on the content of change details and the Specs page since 3.0.0.
Fixed the "Merged" times in the "Completed changes" list all becoming the same after a project was cloned or copied.
Fixed initialization failures showing nothing on screen; an error message is now displayed.
Fixed layout issues:
Change detail headers squeezed to one character per line when the window is narrow.
Project icons without a custom icon squashed when the window isn't tall enough.
The buttons at the bottom of the left sidebar not staying at the bottom when no project is open.
The traffic-light buttons at the top left of the window not vertically centered on macOS.
Fixed Spectra still writing no-longer-used vector search entries to .gitignore; opening a project now also removes the ones written earlier.
Fixed spectra new artifact spec rejecting capability names that other commands accept.
Fixed the file list written into specs at archive time (@trace) picking up edits from other changes or unrelated edits in the same working directory. When spectra task done records exist, it now lists only the files this change modified.
Fixed spectra drift lowering the score of changes that weren't behind.
Fixed the creator and archiver recorded for a change using the identity from the global settings in some git repos, instead of the identity the repo actually uses.
Fixed some records not moving along when renaming a change in the desktop app.