openspec-verify-change

To verify code changes align with delta specs before archiving, you map change artifacts to implementation to identify alignment gaps. This generates a structured verification report with CRITICAL, WARNING, and SUGGESTION findings to reduce drift and rework.

Pre-archive change validation is the process of mapping delta specs, tasks, and design artifacts to code to ensure software changes align with their documentation. It validates the presence of delta specs and generates a structured traceability report.

Yes, you can run artifact traceability verification across CI pipelines to identify alignment gaps between a change's artifacts and its implementation. It validates delta specs presence and maps requirements to code artifacts in codebases and documentation reviews.

You generate a structured verification report for code review deltas by initiating verification with the change name. The system maps delta specs to code artifacts, verifies coverage, and outputs CRITICAL, WARNING, and SUGGESTION findings.

This verification approach applies only to changes with delta specs, tasks, and design artifacts. If a codebase or documentation review lacks these specific change artifacts, the tool cannot map requirements to code or generate the structured verification report.