openspec-verify-change

To verify code changes align with design specs before archiving, you can automate the process by parsing delta specifications and matching requirements to code references. This generates a structured verification report assessing completeness, correctness, and coherence with actionable recommendations.

Checking task completeness against delta specifications involves loading artifacts from openspec/changes/<name>/specs and parsing task checklists to match requirements with code changes. The process outputs a structured verification report highlighting any gaps before archiving.

Yes, validating change artifacts and requirements mapping requires the openspec CLI. The CLI fetches available changes, loads the change schema and artifacts, and generates the verification report by parsing delta specifications for requirements and scenario coverage.

Design coherence verification works by operating across delta specs, code references, and context artifacts stored under openspec/changes/<name>/specs. It assesses whether the implementation correctly aligns with the change's tasks and designs to prevent inconsistent releases.

Yes, you can assess scenario coverage and requirements mapping by running openspec instructions apply --change "<name>" --json. This loads the specific change artifacts and generates a structured verification report detailing completeness and correctness.

Automated code alignment verification should not be used as a substitute for manual code review but rather as a pre-archiving validation step. It specifically parses delta specifications and task checklists, meaning changes without structured openspec artifacts will not be assessed.