openspec-verify-change

To verify changes against delta specifications before archiving, you can run a verification workflow that uses the openspec CLI to list changes, inspect statuses, and load artifacts to compute findings across Completeness, Correctness, and Coherence.

A change artifact verification report validates that implemented changes align with delta specifications, generating structured findings across Completeness, Correctness, and Coherence to ensure traceability and quality control before archiving.

Yes, you need the openspec CLI and access to change artifacts to validate change readiness for archiving, as the CLI is used to list available changes, inspect statuses, and load the artifact context required to compute verification findings.

You can check if implemented code matches design artifacts by running a verification workflow that fetches artifact context via the openspec CLI and generates a structured report confirming implementation alignment with specified tasks and design artifacts.

The best way to ensure traceability and quality control before archiving is to validate implemented changes against delta specifications using a structured verification report, which confirms alignment with tasks and design artifacts for confident archiving decisions.