openspec-verify-change

Run an automated verification process that compares your change's delta specs, tasks, and design artifacts against the actual implementation to ensure completeness, correctness, and coherence before archiving.

Change artifact validation is the process of checking that a target change's implementation aligns with its specifications, tasks, and design decisions to prevent archiving incomplete work.

Yes, you need the OpenSpec CLI and access to your change artifacts to validate delta specs. The tool analyzes specs, code, and design references stored under openspec/changes/ to produce a structured verification report.

You can generate a structured verification report by running openspec verification for a target change, which automatically compares specs, tasks, and design artifacts against the implementation to output prioritized issues.

The best way to automate QA sign-off is to use a validation workflow that automatically compares specs, tasks, and design artifacts against the actual implementation, generating a report with prioritized issues to ensure coherence.

Change validation fails when archiving incomplete work because the actual implementation has not yet aligned with its specifications, tasks, and design decisions, which the verification process detects and reports as prioritized issues.