opsx-verify-change

To verify code changes against specifications, you validate the implementation completeness and coherence by reviewing OpenSpec artifacts, task lists, and design documentation to identify missing requirements and inconsistencies.

OpenSpec change verification is the process of inspecting defined change artifacts to assess implementation coverage, identifying gaps between code modifications and documented requirements to generate a structured verification report.

You check if your implementation matches OpenSpec requirements by analyzing tasks, scenarios, and design decisions to detect divergences, ensuring code changes align with the defined specifications before safe archiving.

Yes, opsx-verify-change requires openspec CLI access to inspect artifacts, review implementation coverage, and generate structured verification reports for software development workflows.

You need to validate implementation changes against change artifacts when a feature implementation is finished and you require a structured verification report to ensure safe archiving before closing the related change.

The best way to identify missing tasks in software change management is to review defined change artifacts and design documentation, comparing them against implementation changes to detect inconsistencies and gaps.