openspec-verify-change

Verifying code changes against design specs involves mapping delta-spec requirements to implementation evidence to ensure completeness. This process generates a structured verification report assessing correctness and design coherence for archiving decisions.

Delta spec verification is the process of confirming that a change's implementation matches defined artifacts like specs, tasks, and design decisions. It detects gaps and divergences to ensure implementation completeness and coherence before archiving.

You check task fulfillment by validating the implementation against change tasks and delta specs. This generates a comprehensive verification report covering completeness and coherence, detecting any gaps or divergences for auditability.

Yes, OpenSpec verification assesses scenario coverage and verifies design decisions by mapping delta-spec requirements to implementation evidence. It detects gaps and divergences to ensure design coherence across openspec-driven changes.

Use change verification for archiving decisions when you need to confirm an implementation aligns with defined artifacts before completion. It validates delta specs, task fulfillment, and design coherence to support safe archiving.