openspec-verify-change

You can verify code implementation against design specifications by using a validation tool that checks task completion, requirement mapping, and scenario coverage. This ensures your code accurately reflects the specified change artifacts before archiving.

The best way to check if code changes match project requirements before merging is to perform a completeness and correctness validation. This process assesses whether all defined tasks are addressed and if the implementation aligns with specified scenarios.

Spec coverage analysis for code review works by assessing completeness, correctness, and coherence. It analyzes task completion, requirement mapping, scenario coverage, design adherence, and code pattern consistency against your change artifacts.

Yes, you need the openspec CLI to validate implementation compliance. The CLI is required to list changes, check status, and apply instructions for retrieving the design documents, tasks, and requirements artifacts needed for verification.

Yes, you can check code pattern consistency and design adherence automatically through a coherence review. This validates that your implementation correctly follows established design decisions and coding patterns specified in your project artifacts.

Implementation verification fails on spec coverage and requirement mapping when defined tasks are not fully addressed or the code does not align with specified requirements. The validation process detects these discrepancies to prevent archiving incomplete work.