openspec-verify-change

To verify code implementation against change artifacts, you can automatically check completeness, correctness, and coherence by analyzing task completion, requirement coverage, and design adherence using the openspec CLI.

Automated verification ensures code matches specifications by parsing tasks.md, spec requirements, design documents, and scenarios to assess whether all defined requirements are met and the implementation aligns with the intended design.

Yes, you need the openspec CLI installed to verify requirement coverage and task completion, as the verification process requires it to list, status, and apply change instructions to your implementation.

The best way to prevent specification drift before archiving is to run an automated verification check that assesses coherence between your code and change artifacts, ensuring accurate alignment with defined tasks and design documents.

Yes, you can check scenario implementation and task completion for a specific change by invoking the verification process with the change name, such as verifying the implementation for the change named 'user-authentication-flow'.