openspec-verify-change

To verify implementation matches change specifications, use a verification skill that checks completeness, correctness, and coherence of code against design documents, specs, and tasks. It ensures all development tasks are done and requirements are covered before finalizing a change.

Checking implementation alignment with design documents involves assessing whether the code follows established architectural patterns and meets documented requirements. A verification skill performs a coherence review to confirm adherence to design decisions and code patterns.

Yes, you need the openspec CLI to verify change artifacts. The CLI is required to list changes, check status, and apply instructions for loading artifacts during the implementation verification process.

You can validate that all development tasks are completed and requirements are covered by running a completeness check. This verification process assesses the implementation against specified change artifacts to confirm full task completion and requirement coverage.

An implementation check against change artifacts should be used before a change is finalized or archived. It prevents inconsistencies and errors by ensuring code accurately reflects the intended design, specifications, and tasks within the development workflow.