openspec-verify-change

To verify implementation correctness against OpenSpec change artifacts, provide the change name to load specs, tasks, and design artifacts from the corresponding folder, generating a structured verification report detailing completeness and coherence.

Delta spec inspection reads delta specs from openspec/changes/<name>/specs/ to identify requirements and scenarios that require code coverage, ensuring that implementation changes are properly mapped and validated before archiving.

Yes, the OpenSpec CLI is required to generate and read context for verification reporting. It builds the structured report detailing task completion, requirement coverage, and design alignment by parsing context files and artifacts.

To check if specs and tasks are implemented, the verification process compares artifacts from the OpenSpec change folder against the codebase, validating that design artifacts are properly mapped to code and emitting a coverage report.

Artifact-based verification should be run before archiving a change to ensure completeness, correctness, and coherence, confirming that the implementation matches the produced specs, tasks, and design artifacts.

Verification is limited to changes that include specs, tasks, and design artifacts, and it requires the OpenSpec CLI to generate context files, meaning it cannot validate changes lacking these structured artifacts or CLI support.