openspec-verify-change

You can verify code changes against openspec delta specs by parsing the delta specs, inspecting task lists, and reviewing design decisions to identify discrepancies. This generates a structured verification report with prioritized issues before archiving.

To check alignment between implementation artifacts and change specs, validate the code, tests, and design against delta specs to ensure the change is fully realized. This process highlights critical gaps and provides actionable recommendations for completeness.

Yes, you can validate openspec changes without a formal design.md file. The verification process checks the availability and consistency of tasks, specs, and design decisions across the change directory with or without it.

A verification report includes identified discrepancies between implementation changes and their corresponding artifacts, highlighting critical gaps and actionable recommendations. It ensures completeness and coherence by validating alignment with delta specs.

To ensure task lists and specs are consistent before archiving a change, check their availability and consistency across the change directory. The verification process validates alignment with delta specs to confirm the change is fully realized.

Yes, you need to provide the change name to start the verification workflow. This allows the process to inspect task lists, parse delta specs, and review design decisions to generate a structured verification report.