openspec-verify-change

To verify implementation matches change artifacts, validate the alignment between your code and delta specs, tasks, and design. This generates a structured verification report detailing completeness, correctness, and coherence findings with concrete remediation recommendations.

Checking completeness and correctness across delta specs involves applying the openspec workflow to retrieve change artifacts, inspect their presence, and assess coherence. This produces a structured report highlighting critical issues, warnings, and suggestions with file references.

Generating a verification report for missing artifacts and divergences requires inspecting your target change against its specs and tasks. The process assesses completeness, correctness, and design-consistency to produce structured CRITICAL, WARNING, and SUGGESTION findings.

Yes, you can use openspec to validate code alignment with tasks and design documents. The workflow retrieves the relevant change artifacts, inspects their presence, and assesses whether the implementation is complete, correct, and coherent before archiving.

Your implementation diverges from design specs and tasks due to missing artifacts, incorrect code alignment, or coherence issues across delta specs. A structured verification report identifies these specific divergences and provides concrete recommendations for remediation.