openspec-verify-change

To verify a change before archiving, compare the implementation against delta specs, task lists, and design decisions. Run openspec status and openspec instructions apply on the change directory to generate a structured report identifying missing implementations and incomplete tasks.

Delta-spec driven verification is the process of comparing delta specs to the codebase to detect missing implementations. It assesses completeness, correctness, and coherence by checking task lists and design decisions against the actual software change before archiving.

Yes, you need the openspec CLI to check change implementation completeness. The tool requires the CLI and context files under openspec/changes/<change-name>/ to run status checks, fetch artifacts, and produce a structured verification report with actionable remediation guidance.

To fix implementation gaps found during change verification, follow the guided remediation in the generated report. It provides actionable recommendations with specific file references to address missing implementations and testing shortfalls before archiving the change.

No, openspec verification requires context files located specifically under openspec/changes/<change-name>/. The tool depends on this directory structure to load metadata, fetch artifacts, and produce a structured verification report for delta-spec driven changes.