openspec-verify-change

Verifying implementation against specs requires checking that code aligns with specified change artifacts like tasks, requirements, scenarios, and design documents. This process assesses completeness and correctness, generating a detailed report with actionable recommendations for critical, warning, and suggestion-level issues.

To check if code changes meet requirements before merging, run a verification process that assesses completeness, correctness, and coherence against change artifacts. It flags critical, warning, and suggestion-level issues to prevent divergence and ensure quality before archiving the code.

Yes, you need the openspec CLI to verify change artifacts. The verification process requires the openspec CLI specifically for artifact retrieval and status checks to accurately assess whether your code implementations align with specified tasks, requirements, scenarios, and design documents.

Compliance verification for code review and change management ensures that code implementations accurately reflect design specifications, tasks, and other change artifacts. It prevents divergence and ensures quality before archiving by identifying critical, warning, and suggestion-level issues with actionable recommendations.

The best way to ensure feature implementation aligns with approved design documents is to perform automated verification checking completeness, correctness, and coherence. This generates a detailed report with actionable recommendations for any critical, warning, or suggestion-level issues before merging.

Code implementation diverges from specifications during development when completeness, correctness, and coherence against change artifacts are not verified. Automated verification identifies these divergences and provides actionable recommendations to ensure alignment before archiving.