openspec-verify-change

You can verify code implementation against change artifacts by checking task completion for completeness, mapping requirements to code for correctness, and ensuring design adherence for coherence before archiving.

Automated compliance checking for change management flags incomplete tasks, unimplemented requirements, design deviations, and code pattern inconsistencies between the actual implementation and the specified change artifacts.

You need to run verification checks on change artifacts before merging a new feature to automatically verify that all associated tasks are done, requirements are correctly implemented, and design principles are strictly followed.

Yes, you need the openspec CLI installed for artifact management and status checks, as it is a required dependency to verify implementation completeness, correctness, and coherence against your change artifacts.

Checking if code implementations adhere to project design principles involves verifying coherence by ensuring design adherence and maintaining code pattern consistency across all mapped requirements and scenarios.

The best way to prevent discrepancies between specifications and code before archiving is to perform automated verification that evaluates completeness, correctness, and coherence to catch unimplemented requirements and design deviations early.