Run spec-driven coding changes with Spectra skills and CLI
Manage proposal, implementation, verification, review, audit, drift, archive, and commit steps through Spectra's agent skills and CLI-backed spec workflow.
npx skills add agentskillexchange/skills --skill run-spec-driven-coding-changes-with-spectra-skills-and-cli
npm install -g @kaochenlong/spxa, run spxa init in the target repository, then invoke the documented agent skills such as $spectra-propose, $spectra-apply, $spectra-verify, $spectra-review, $spectra-audit, $spectra-drift, $spectra-archive, or $spectra-commit.Use Spectra when a coding agent should run a change through a structured spec-driven workflow instead of ad hoc chat, loose Markdown files, or a normal desktop spec manager. The agent can discuss requirements, create proposals, apply task lists, ingest requirement changes, verify implementation against specs and design, review code, audit changed code, detect drift, archive completed changes, and commit only files that belong to the change. Invoke it when the operator needs a repeatable change lifecycle with visible spec and task state across Codex, Claude Code, Cursor, Copilot, Antigravity, or Junie. The boundary is the agent-operated SDD change workflow using Spectra skills and the spxa/spectra tooling; it is not just a desktop product listing or a generic spec-writing template.
What this skill actually does
Inputs and prerequisites: Node.js 22.14+ for the spxa CLI, optional Spectra desktop app, Codex, Claude Code, Cursor, GitHub Copilot, Antigravity, or JetBrains Junie.
Setup notes: Install the CLI with npm install -g @kaochenlong/spxa , run spxa init in the target repository, then invoke the documented agent skills such as $spectra-propose , $spectra-apply , $spectra-verify , $spectra-review , $spectra-audit , $spectra-drift , $spectra-archive , or $spectra-commit .
Source and verification boundary: use https://github.com/kaochenlong/spectra-app as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.