openspec-verify-change

To verify code changes against specifications, you can cross-reference contextFiles with delta specifications and design decisions to assess task completion and spec coverage. This generates a structured verification report detailing completeness, correctness, and coherence with actionable recommendations for any gaps found.

Change artifact validation is the process of ensuring an implemented change aligns with its specifications, tasks, and design decisions before archiving. It cross-checks requirements and scenarios against the codebase and tests to reduce the risk of unimplemented or incoherent changes.

To check if your task list is complete and consistent with delta specs, load your change artifacts and cross-reference the contextFiles with the delta specifications. This validation process identifies any missing tasks or inconsistencies between the implementation and the planned design.

Yes, you can generate a structured verification report for spec coverage gaps by cross-referencing your codebase and tests against requirements and scenarios. The report details completeness, correctness, and coherence, providing actionable recommendations for any identified gaps.

Yes, this change validation process works without external dependencies. It loads the target change artifacts directly and assesses task completion, spec coverage, and coherence by cross-referencing contextFiles with delta specifications and design decisions to produce a structured verification report.

You should use change implementation verification before archiving a change to reduce the risk of unimplemented or incoherent updates. It validates that task lists are complete, cross-checks requirements against the codebase, and ensures the implementation aligns with all change artifacts.