openspec-verify-change

To verify changes against specs before archiving, you provide the change name and run a verification workflow that reads available artifacts to produce a coherence report outlining completeness, correctness, and design adherence.

Change-artifact alignment validation is the process of ensuring a change implementation matches its associated specs, tasks, and design documents, reducing the risk of undetected gaps before archiving.

You check implementation completeness by applying a verification workflow to a specified change, which inspects available artifacts and reports actionable recommendations for any missing task completions or design inconsistencies.

Yes, you can get actionable remediation steps for missing task completions by running the artifact-driven validation workflow, which automatically reads available changes and reports status, completeness, and coherence.

Yes, verifying changes requires explicit user selection for the change, ensuring the tool reads the correct context files and generates a report strictly for the specified implementation.

You should run a coherence report for a change submission right before archiving to catch missing task completions or design inconsistencies and ensure the implementation is complete, coherent, and aligned with its change artifacts.