openspec-verify-change

To verify change implementations before archiving, you can use OpenSpec CLI to load change context, validate produced artifacts against intended outputs, and generate a multi-dimensional verification report highlighting completeness, correctness, and consistency.

Change verification for OpenSpec projects is the process of comparing code changes, specs, and tasks against a change's intended outputs during archiving or release preparation to ensure alignment and reduce the risk of missing requirements.

To check archiving readiness for OpenSpec changes, run the verification flow for a target change name and review the resulting structured report to confirm that completeness, correctness, and consistency requirements are fully satisfied.

Yes, OpenSpec CLI supports context-aware validation by loading change context to identify required artifacts, including tasks, specs, and designs, ensuring that all produced components align with the intended outputs.

The best way to align code changes with intended outputs in spec-driven development is applying a structured verification flow that compares implemented tasks and designs against the change's original specifications before archiving.

OpenSpec change archiving may fail due to missing requirements when implemented changes lack alignment with intended outputs, which is why running a change verification check helps identify unsatisfied dependencies and incomplete artifacts beforehand.