openspec-verify-change

To verify implementation artifacts, you process change tasks and specifications to check correctness, completeness, and coherence. This ensures your code implementation aligns with associated change artifacts before archiving.

Change verification is the process of validating that code implementation matches change specifications and design artifacts. It checks for completeness, correctness, and coherence to ensure the implementation is ready for archiving.

Yes, you need the openspec CLI installed to validate implementation context. The verification process depends on this CLI to process change artifacts, tasks, and specifications for validation.

You check implementation alignment by running automated verification against change artifacts. This validates that your code correctly and completely fulfills the associated tasks and design specifications.

Automating implementation validation involves processing change artifacts, tasks, and specifications through a verification CLI. This validates coherence and completeness automatically, ensuring the implementation matches the design before archiving.

You need specification checking during code review when preparing to archive changes. It verifies that the implementation is complete, correct, and coherent with the associated tasks and specifications.