openspec-verify-change

To verify implementation completeness, run a verification pass that compares the code against change artifacts, checking task checkboxes, delta specs, and design coherence to produce a structured scorecard with prioritized remediation issues.

Change verification is the process of validating that an implementation correctly reflects an intended change by loading its artifact set, parsing delta specs, and checking code references to surface critical gaps and alignment issues.

Check spec coverage by loading the artifact set, parsing delta specs, and evaluating code references against task status indicators to confirm alignment and identify any missing or incomplete implementation evidence.

Yes, you can generate a structured verification report that includes a concise scorecard, prioritized issues, and specific file references to guide remediation of code review gaps and missing design artifacts.

Change verification works without external dependencies by directly loading and parsing existing artifact files, analyzing task statuses, and evaluating spec coherence internally to produce the verification scorecard.