openspec-verify-change

To verify code changes match delta specs before archiving, you can validate delta-spec alignment by comparing implemented changes against defined requirements, mapping each requirement to its code change, and generating a structured verification report highlighting gaps and coverage.

Delta spec validation in change management is the process of checking that a change's implementation matches its specifications, tasks, and design. It ensures delta specs exist, maps requirements to code, and checks task completion before archiving.

Yes, you can use spec validation for code reviews on large changes. It maps each requirement to its associated code changes and tasks, generating traceability and a structured verification report that highlights gaps, coverage, and risk for archive decisions.

You generate a traceability report for requirement mapping by mapping each requirement to its code change and associated tasks. This process produces a structured verification report highlighting gaps, coverage, and risk for governance checks and archive decisions.

Yes, openspec-verify-change works for compliance governance checks. It validates that a change's implementation matches delta specs and tasks before archiving, generating a structured verification report that highlights gaps, coverage, and risk for release cycles.

The best way to check task completion before archiving a change is to run a validation process that ensures delta specs exist, maps requirements to code, and generates a structured verification report highlighting gaps, coverage, and risk for archive decisions.