openspec-verify-change

To verify code changes match specs before archiving, run an automated validation workflow that cross-checks delta specs, task checklists, and design decisions against your implementation. This process assesses completeness, correctness, and code-pattern coherence to ensure full requirement coverage.

Validating task completion and spec coverage involves parsing task checklists and mapping delta requirements to code and tests. An automated verification workflow reads change artifacts from context to identify gaps and outputs a structured report confirming alignment with design decisions.

Artifact mapping for change verification works by parsing delta specs with requirements and scenarios, then cross-checking them against code and tests. It identifies gaps in task checklists and design decisions, ensuring implementation coherence before generating a structured verification report.

Yes, you can run design alignment checks without external dependencies. The verification workflow operates independently, reading change artifacts directly from context to parse task checklists, delta specs, and design decisions to validate code-pattern coherence.

You need to run a change verification report before archiving a code change produced via the openspec workflow. Running it validates that all requirements are addressed, implementation aligns with the change's design, and task checklists are fully complete.

Code changes fail spec coverage validation when implementation lacks coherence with delta specs, task checklists, or design decisions. The verification process identifies these gaps by cross-checking artifact requirements against code and tests, highlighting missing scenarios in the structured report.