openspec-verify-change
Checks that the implementation matches the change artifacts (specs, tasks, design) before archiving.
- Kind
- Skill
- Works with
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini / Antigravity, Windsurf / Devin, Cline, Kiro
- Source
- Fission-AI/OpenSpec @ 79b6aa9c98f1
- Path
- skills/openspec-verify-change/SKILL.md
- License
- MIT
- Jobs
- Review
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
Verify that an implementation matches the change artifacts (specs, tasks, design). **Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`, `schemas`, `view`). Once selected, treat `--store <id>` as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run `openspec status --change "<name>" --json --store "<id>"`, not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root. …