openspec-verify-change

To verify code changes against delta specs before archiving, load change artifacts from contextFiles and generate a formal verification report checking task completion, spec coverage, and implementation mapping. This enforces correctness and coherence before the archive step.

Spec-driven workflow verification is the process of checking that a code implementation aligns with delta specs, tasks, and design patterns. It validates scenario coverage and design coherence, producing concrete recommendations and file references to fix any gaps.

Check implementation coverage by parsing delta specs for requirements and scenarios, then validating the code against these artifacts. The verification process maps implementations to specs to identify gaps and provides actionable file references for any missing coverage.

Yes, you can generate a structured verification report that identifies divergences between code and design artifacts. The report enforces coherence through design pattern adherence checks and provides concrete recommendations with file references to resolve any misalignments.

Yes, change verification requires contextFiles to load the necessary artifacts. The workflow checks the status of listed changes, loads these artifacts to parse delta specs, and validates the implementation against the loaded tasks and design requirements.