openspec-verify-change

To verify code implementation against change specifications, use a validation process that checks task completeness, correctness against spec intent, and coherence with design documents. This pre-archival quality assurance ensures the code accurately reflects defined requirements and approved architecture.

Change verification in quality assurance is the process of validating code implementation against change artifacts like specifications, tasks, and design documents. It ensures completeness, correctness, and coherence within a project before archiving or merging new features.

Yes, you need openspec-cli to validate implementation against specs. The validation process scopes to changes within a project managed by the openspec CLI, relying on its infrastructure to access change artifacts and verify adherence to development standards.

To check if all user stories and tasks are implemented, perform a completeness check and correctness validation against the change specifications. This confirms all requirements are addressed, the code matches spec intent, and necessary tests are in place.

The best way to ensure code follows approved architecture is to perform a coherence review during change verification. This checks adherence to design decisions and code patterns, confirming the implementation matches the approved architecture and design documents.

Implementation may not match change specifications due to incomplete tasks, unaddressed requirements, or deviations from design decisions. Running a verification check identifies these gaps in completeness, correctness, and coherence before archiving.