openspec-verify-change

To verify code changes against design specs, you need a tool that compares delta specs, tasks, and codebase artifacts to determine completeness and coherence. This process generates a structured verification report with prioritized, actionable recommendations and file paths for any gaps or divergences.

A structured verification report for change implementations identifies gaps, incomplete tasks, and design deviations by comparing code against specs. It categorizes issues into CRITICAL, WARNING, and SUGGESTION levels, providing file and line references for targeted remediation.

You can identify missing requirement implementations by analyzing context artifacts and delta specs across the codebase. This comparison validates completeness and correctness, returning a prioritized set of actionable recommendations with exact file paths and line references for any found gaps.

You need to validate change implementations against specs before archiving or releasing a change. This ensures the implementation aligns with associated tasks, design artifacts, and delta specs, verifying overall coherence and preventing incomplete requirements from progressing.

Yes, validating change implementations against specs can produce file and line references for design deviations. By operating across delta specs and the codebase, it generates a structured report with prioritized, actionable recommendations for precise remediation.