One loop for each change
Running apply approves the change.
Propose
/sparc:proposeProposal, specs, design and tasks.
Stops: Decisions get lost.
Product owner, architect, UX designerApply
/sparc:applyTests first, then the code.
Stops: The agent guesses.
Software engineerReview
qa.mdA fresh agent reads the diff.
Stops: The agent reviews its own work.
Software engineerQA
qa.mdA test for each scenario.
Stops: No test proves the spec.
QA engineerVerify
hooks/hooks.jsonLint, tests and evidence must pass.
Stops: "Done" without proof.
Verifier, no LLMArchive
/sparc:archiveSpecs and documents in sync.
Stops: Documents drift from the code.
Product owner, architectRelease
/sparc:releaseVersion, changelog and tag.
Stops: Version and changelog disagree.
You
Each document has one owner
/sparc:init adds these files. A role is a rule file that a skill follows.
| File | Holds | Format | Owner |
|---|---|---|---|
openspec/specs/ | Required behavior | OpenSpec | Product owner |
docs/backlog.md | Open items | Markdown | Product owner |
docs/adr/ | Decisions | MADR | Architect |
docs/architecture/ | Context, containers, risks | C4, canvas | Architect |
docs/mockups/ | Interface drafts | HTML | UX designer |
qa.md | Proof for each scenario | Markdown | QA engineer |
CHANGELOG.md | Done work for each release | Keep a Changelog | Product owner |
sparc is built with sparc
Each change to sparc went through this loop.
- Decisions
- 18 ADRs
- Changes archived
- 21
- Releases
- 9, latest 0.9.0
- Check dependencies
- 0 npm packages
| Archived | Change |
|---|---|
| 2026-11-18 | use-node-lts |
| 2026-11-18 | support-github-copilot |
| 2026-11-18 | deploy-website-on-release |
Questions
Which coding agents does sparc support?
Claude Code (CLI and Claude Desktop) and GitHub Copilot CLI. The README tells what is not tested with Copilot, for example Copilot in VS Code and the cloud agent: Supported Agents.
Can I use sparc in an existing code base?
Yes. Run /sparc:init in the folder of the project. The architect documents what it finds in the code.
Must a small fix go through the full loop?
Yes. Each change of behavior goes through propose, apply and archive. This is the cost of specs and documents that stay correct.
Does sparc work with pull requests?
Yes. Choose the workflow trunk or pull-request in openspec/config.yaml. In the pull request workflow, the review or the merge is the approval.
Start a project
In Claude Desktop, add sparc with Plugins, then Add from repo.
Open the folder of your project. Tell the idea one time.
/sparc:init <project idea>Propose each feature or fix. Then apply and archive it.
/sparc:propose <feature>