openspec-verify-change

Verifying implementation against change artifacts involves checking completeness, correctness, and coherence between code and specifications. This process generates a structured report highlighting critical issues, warnings, and suggestions before archiving.

Implementation verification in change management ensures code accurately reflects intended changes defined in specifications, tasks, and designs. It prevents inconsistencies by validating that all associated tasks are completed and requirements are met.

Yes, you need the openspec CLI to perform status checks, apply instructions, and list available changes. The CLI provides the necessary commands to scope and validate that your implementation correctly aligns with the defined change artifacts.

To check if completed tasks align with design documents, run an automated verification process against your change artifacts. This validates that your implementation meets the defined requirements and produces a detailed report of any discrepancies.

The best way to automate code review for new feature specifications is to use a verification tool that cross-references your implementation with change artifacts. This automatically identifies missing requirements and structural inconsistencies before merging.

Implementation verification reports warnings during change management to highlight potential coherence issues between your code and design documents that are not critical failures. These warnings suggest improvements to ensure full alignment before archiving the changes.