openspec-verify-change

To verify implementation against change specifications, you can use this skill to perform integrity, correctness, and consistency checks on code and documentation. It validates that all tasks are completed and requirements are met before code merge or release.

Change management verification checks for completeness, correctness, and consistency in development workflows. It ensures the software implementation accurately matches defined specifications, tasks, and designs, flagging any discrepancies before archiving.

You check implementation adherence by running consistency verification against your change artifacts. This process validates whether the implemented features align with approved design documents and user stories, preventing inconsistencies and errors.

Yes, you need the openspec CLI to validate implementation completeness. The verification process requires the openspec CLI to list, status, and apply changes, and performs integrity checks on code and documentation.

The best way to ensure code matches approved design documents is to run pre-archival verification. This automatically validates that implemented features align with user stories and design decisions, flagging discrepancies for correction.

Implementation verification fails when tasks are not completed because the integrity check validates that all requirements are met. The verification process ensures software implementations accurately match defined specifications and tasks before archiving.