openspec-verify-change

You can verify code implementations against change specifications by running automated checks that compare code against change artifacts. This identifies incomplete tasks, missing requirements, and design deviations to ensure code accurately reflects intended changes.

Code implementation verification ensures code accurately reflects changes defined in specifications, tasks, and designs. You need it after implementing a feature and before merging changes to prevent drift and ensure quality by flagging unmet requirements.

Yes, you need the openspec CLI to check if your code matches design documents. The CLI is required to list, status, and apply change instructions for retrieving and analyzing the change artifacts used during the verification process.

You can automatically flag incomplete tasks and missing requirements before merging by running a verification check against your change artifacts. This assesses coherence and flags pattern inconsistencies, spec divergences, and unmet requirements automatically.

A limitation of using openspec for change verification is its strict dependency on the openspec CLI for artifact retrieval and analysis. Verification is limited to assessing coherence against existing change artifacts, meaning missing specifications cannot be assessed.