openspec-verify-change

To verify code changes match specs before archiving, run an automated consistency check that cross-checks implementations against delta specs, tasks, and design artifacts. It loads change artifacts via the openspec CLI to check completeness, correctness, and coherence across the codebase and tests.

Artifact-driven change verification is the process of cross-checking code, tests, and tasks against updated delta specs to ensure full traceability. It detects missing coverage or deviations between specifications and implementations to guide remediation before archiving.

Yes, you need the openspec CLI to run spec-validation. The verification process requires the openspec CLI and access to the change artifacts to load the specified change context and perform completeness and coherence checks.

To check implementation completeness against a change context, execute the openspec CLI with the change name. The Skill loads artifacts and checks completeness, correctness, and coherence across the codebase and tests to confirm all requirements are implemented.

Yes, automated spec validation detects missing test coverage. It cross-checks code, tests, and tasks against updated delta specs to identify missing coverage or deviations between specifications and implementations, guiding necessary remediation.

You should run change verification when a change is ready for review. Running the verification confirms all requirements are implemented and linked to code changes, reducing misalignment and regressions before archiving.