openspec-verify-change

To verify code changes against delta specifications, you can run a verifier on the selected change to parse requirements and map them directly to code changes. This produces a structured, actionable report ensuring completeness and coherence before archiving.

Checking design documentation coverage involves assessing task completion, scenario coverage, and design coherence across code and tests. A structured verification report identifies gaps and provides actionable recommendations to ensure full implementation alignment.

Generating a structured report for openspec change compliance requires reading delta specs from openspec/changes/<name>/specs and loading context artifacts. The verifier outputs recommendations detailing completeness, correctness, and coherence across the implementation.

The openspec verification process applies to changes with delta specs, tasks, and design documentation. Without existing design documentation, the verifier cannot fully assess coherence and completeness across code, tests, and design decisions.

A change implementation fails delta spec compliance checks when task completion is incomplete, scenario coverage is missing, or design decisions lack coherence. The verification report identifies these specific gaps and provides actionable recommendations to resolve them.