openspec-verify-change

To verify implementation against specifications, you can run automated checks that validate completeness, correctness, and design coherence against your change artifacts. This ensures your code matches the intended requirements before archiving.

Change implementation verification is a quality assurance process that validates your code matches its associated specifications and tasks. It prevents design misalignment issues by checking that all requirements are implemented correctly.

You can check that implementation tasks match change specifications by running a verification command with the change name. This applies automated checks to confirm all tasks are complete and requirements are correctly implemented.

Yes, you need the OpenSpec CLI to interpret change context and apply verification checks. The CLI provides the necessary framework to validate completeness, correctness, and design coherence against your specifications.

The best way to ensure code correctness before archiving is to run automated verification checks against your change artifacts. This validates that your implementation aligns with the intended design and that all specified tasks are complete.

Implementation verification may fail on design coherence when your code does not align with the associated specifications and tasks. The verification process checks for completeness and correctness, flagging any deviations from the intended design.