openspec-verify-change

To verify code against change artifacts like specs and design documents, use an automated verification skill to check completeness, correctness, and coherence. It flags incomplete tasks, unimplemented requirements, and design divergences before merging changes.

Preventing code drift requires automated verification of code implementation against change artifacts including specs, tasks, and design documents. This process ensures adherence to predefined specifications and flags pattern inconsistencies before archiving.

Yes, checking for unimplemented requirements requires the OpenSpec CLI to fetch and parse change-related files and code. This prerequisite allows the verification process to accurately identify incomplete tasks and design divergences.

You can automatically flag incomplete tasks and design divergences after implementing a new feature by running a verification check against your design.md and tasks.md files. This ensures all requirements are met and the implementation aligns with the design.

Yes, automated code verification works with tasks.md and design.md files to ensure completeness and correctness. It applies to software development workflows requiring adherence to predefined specifications and design principles before merging changes.