openspec-verify-change

You can verify code changes against delta specs by providing the target change name, which triggers a search of the codebase for specification alignment, scenario coverage, and design conformity before generating a structured verification report with actionable findings.

Change artifact validation assesses software changes for Completeness, Correctness, and Coherence by mapping requirements to implementations, identifying divergences, and checking design adherence against project standards before archiving.

You can check if your implementation matches tasks.md and design specs through a validation workflow that verifies all change artifacts are present, maps defined work items to code, and flags uncovered scenarios for remediation.

Yes, you can assess code pattern consistency using the Coherence review feature, which checks design adherence and verifies that the implementation patterns align with established project standards.

The best way to identify divergences between requirements and code is to perform a Correctness assessment that maps requirements to implementations and flags uncovered scenarios for remediation.

Yes, the verification workflow applies to changes with varying levels of artifacts, including tasks.md and specs, so it can still validate Completeness and Correctness even when design documents are missing.