openspec-verify-change
Verify implementation matches OpenSpec change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving. Also use when the user says "openspec verify" or "opsx verify".
Install
With your agent
Install OMGSkills skill "fission-ai/openspec:openspec-verify-change" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/Fission-AI/OpenSpec /tmp/OpenSpec && ln -s /tmp/OpenSpec/skills/openspec-verify-change ~/.claude/skills/openspec-verify-changeFrom README
Verification Report: Summary | Dimension | Status | |--------------|------------------| | Completeness | X/Y tasks, N reqs| | Correctness | M/N reqs covered | | Coherence | Followed/Issues | In each Status cell, report the results of checks that ran and Not verified ( ) for every skipped check. If all checks in a dimension were skipped, start the cell with Not verified. Never score a skipped check as passing. Treat every not verified or partially verified check as skipped in the final assessment. Count only ADDED and MODIFIED requirements in N, and report REMOVED and RENAMED requirements separately (for example, "1 removal confirmed, 1 rename verified", or "1 removal not verified (baseline unavailable)"). For a change that only removes or renames requirements, the Correctness cell reads Not applicable (no ADDED or MODIFIED requirements).
More from this repo
draft-openspec-docs
Collaborative page-drafting mode for the OpenSpec docs.
release-openspec
Used when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is...
openspec-apply-change
Implement tasks from an OpenSpec change.