Spectra CLI
The spxa CLI and a skill set for spec-driven development in Claude Code, Codex and Cursor, from a change proposal to the archive
- 767 ★ on the repository
- Last commit
Extended access
Why this level
- The skills give the agent `/spectra-apply` and `/spectra-commit`, which edit project files and create Git commits
- Installation pulls a native binary from npm, and the CLI updates itself with `self-update`
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/spectraDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The skills give the agent `/spectra-apply` and `/spectra-commit`, which edit project files and create Git commits
- Installation pulls a native binary from npm, and the CLI updates itself with `self-update`
This is third-party code. Review the repository files before installing.
What it does
Spectra runs a change through specs. The agent writes a proposal, requirements, a design and a task list, implements the tasks, checks the code against the specs and closes the change by merging new requirements into the main ones. State lives in Markdown files, and a task list with `- [ ]` and `- [x]` marks gives progress. The CLI is called `spxa` and installs from npm. `spxa init` creates skills in the project for the agents you choose: Claude Code, Codex, Cursor, GitHub Copilot, Antigravity and JetBrains Junie. The skills are invoked as `/spectra-propose`, `/spectra-apply`, `/spectra-verify`, `/spectra-analyze`, `/spectra-review`, `/spectra-audit`, `/spectra-debug`, `/spectra-archive` and `/spectra-commit`. Codex uses `$` instead of the slash. There is also a desktop app for macOS and Windows: it shows specs and tasks, opens a compact floating panel with progress and archives a finished change in one action. The `spectra park` and `spectra unpark` commands set aside an unfinished change without cluttering the Git working tree.
Who it is for. For developers who give Claude Code, Codex or Cursor large changes and want to agree on requirements and a plan with the agent before it starts writing code.
Good fit when
- A change touches several modules and needs agreed requirements, design and a task list before any code
- The agent should implement tasks one by one and tick them off while you watch progress
- Before closing a change you want the code checked against specs, tasks and design with `/spectra-verify`
- Work stopped halfway and the unfinished change needs to be set aside with `spectra park`
- You want one workflow across Claude Code, Codex and Cursor
Not a fit when
- A two-line fix: a proposal, design and tasks cost more time than the edit itself
- Your team already works with OpenSpec or Spec Kit: Spectra grew out of OpenSpec but uses different commands and a different folder layout
- You work on Linux and want the desktop app: it ships for macOS and Windows only, and Linux gets the CLI
- Commercial distribution needs a license your lawyers have checked: you will have to read the terms in the `LICENSE` file yourself
Example request
/spectra-propose Add a CSV export of orders with a period picker to the account page.Limitations
The CLI needs Node.js 22.14 or newer. Native binaries ship for macOS, Linux and Windows, but the author has verified runs only on macOS arm64 and Linux glibc 2.31, while the macOS x64 and Windows x64 builds have not been run yet. Linux on musl and Windows arm64 are unsupported: the launcher exits with `SPXA_UNSUPPORTED_RUNTIME`.
The `spxa` command and the app that installs `spectra` update independently. The skills call `spxa` directly, so it must be installed globally, because `npx` leaves no permanent command. GitHub could not detect the license type, and MIT covers only the small Node.js launcher. The repository was last updated on 13 September 2026.
How to disable. Remove the CLI with `npm uninstall -g @kaochenlong/spxa` and delete the skills `spxa init` created from the project and agent skill folders. The macOS app is removed with `brew uninstall --cask spectra-app`.
FAQ
How do I install Spectra for Claude Code?
Run `npm install -g @kaochenlong/spxa`, then `spxa init` in the project root and tick Claude Code. Skills with the `/spectra-` prefix appear in the project, while the macOS app installs separately with `brew install --cask spectra-app`.
Do I need the desktop app for the `spxa` CLI to work?
No. The npm CLI ships its own binary and the agent skills, and the app only shows specs and progress. The commands differ: `spxa` from npm and `spectra` from the app.
How is Spectra different from OpenSpec?
Spectra began as a GUI for OpenSpec, then the author rewrote the workflow to suit his habits: simpler commands, parallel task execution and skills for verification, review, audit and debugging.
Which agents does Spectra support?
Claude Code, Codex, Cursor, GitHub Copilot, Antigravity and JetBrains Junie. `/spectra-verify` and `/spectra-analyze` can be run directly in Claude Code, Codex and GitHub Copilot.
Can Spectra run tasks in parallel?
Yes. `/spectra-propose` records task dependencies as `[after: ...]`, and `/spectra-apply` hands ready tasks to subagents. Without subagents the tasks run one by one.
Discussion
No questions or reviews yet.
Related
CLI toolsA CLI for spec-driven development: the agent carries a task through files in the repository from plan to verification and archive
Spec-driven development for coding agents: proposal, requirements, design and tasks come before any code
A CLI, MCP server and skill for spec-driven development: short markdown specs, a task board and search that an agent can read.
A plugin with three skills for large development work: project analysis, phased tasks tracked as GitHub Issues, parallel agents and code review
A skill that interviews you and writes requirements.md, design.md and tasks.md so Claude Code and Cursor work from one plan
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Comparison with similar tools
Cards that share the main search query, and how they differ.
README in short
The author built Spectra around his own development rhythm and split the work into stages: planning, implementation, quality gates and finishing. You can install it three ways: Homebrew for the app, npm for the CLI alone, or ready builds from the releases page. The app interface is available in English, Japanese and Chinese.