openspec-verify-change

To verify code implementation against change artifacts, you can check that code aligns with specified specs, tasks, and design documents. This process assesses completeness, correctness, and coherence to prevent inconsistencies before archiving changes.

Change artifact verification is the process of ensuring code implementations accurately reflect intended changes defined in specifications and designs. It checks task completion, maps requirements to implementations, and ensures design adherence to prevent inconsistencies.

Yes, you need the openspec CLI to perform status checks and retrieve artifacts for implementation verification. The CLI provides the necessary artifact retrieval and status functions required to assess code alignment with change specifications.

Yes, you can automatically check spec coverage and task completion for a new feature. Automated verification flags incomplete tasks, spec or design divergences, and pattern inconsistencies to confirm all defined requirements are properly implemented.

When verifying implementation coherence and correctness, the process identifies incomplete tasks, spec divergences from the approved design, and code pattern inconsistencies. It maps requirements to the implementation to ensure full scenario coverage.

You should use automated verification for change management before archiving or merging a new feature. It ensures all defined requirements are implemented, code adheres to the approved design, and associated tasks are marked as complete.