openspec-verify-change

To verify code changes against specs, an automated verification process checks implementation completeness, correctness, and coherence against change artifacts. It inspects tasks.md, delta specs, and design.md to ensure readiness for archiving or release and catch diverging work early.

Spec-driven verification is the process of validating that a code change implementation matches its change artifacts like specs, tasks, and design documents. It assesses completeness, correctness, and coherence to confirm readiness before archiving or deployment.

Yes, validating change status with this approach requires the openspec CLI. The CLI is used to list changes, retrieve status, and gather context files needed to inspect tasks.md, delta specs, and design.md for completeness assessment.

You can generate an actionable code review report by running a verification check on your selected change. The process produces prioritized CRITICAL, WARNING, and SUGGESTION issues with file references and concrete remediation recommendations to drive fixes and approvals.

Implementation coherence checks cover design adherence and code pattern consistency during spec-driven code review. This dimension ensures the implementation aligns with the documented design and follows established patterns across the codebase.

Yes, automated verification catches missing tasks before archiving by checking task checklists and requirement presence. It reviews available artifacts for the selected change to identify incomplete or diverging work early in the process.