openspec-verify-change

To verify change implementation, validate that your change's tasks, specs, and design align with expected artifacts by assessing completeness, correctness, and coherence using the openspec CLI to load context and generate a structured report.

Change artifact validation is the process of ensuring a change's tasks, specs, and design documents are complete, correct, and coherent before archival. It checks task completion against context and assesses spec coverage against delta specs.

You check spec coverage by loading change context via the openspec CLI and running a structured verification workflow that assesses whether your implementation correctly aligns with the expected delta specs and design artifacts.

Yes, the openspec CLI is required to retrieve status, load context, and assess artifacts. The verification workflow relies on it to validate task completion, spec coverage, and design coherence before archiving.

The best way to ensure design coherence is to apply a structured verification approach across three dimensions: completeness, correctness, and coherence, which produces clear, actionable recommendations for any issues found.

Change verification fails when tasks, specs, or design lack completeness, correctness, or coherence. The workflow identifies these misalignments against expected artifacts and provides actionable recommendations to resolve issues before archiving.