openspec-verify-change

To verify changes against specs before archiving, you can use OpenSpec tooling to compare code and tests against delta specs, ensuring implementation fulfills the associated artifacts and confirming readiness for archiving.

Change verification in OpenSpec is the process of identifying whether an implementation fulfills associated artifacts like specs, tasks, and design to ensure readiness for archiving. It maps requirements to code using a valid change name.

Yes, you need executable verification tasks and delta specs to check change readiness with OpenSpec. The skill applies to changes with these elements, requiring access to change artifacts and a valid change name to map requirements.

You generate a structured verification report by running OpenSpec status and apply commands. This retrieves available changes, loads context, and highlights gaps or divergences with actionable recommendations to fix before archiving.

The best way to ensure spec coverage when validating software changes is through artifact-aware verification, which compares code, tests, and design outputs against delta specs to highlight gaps and divergences with actionable recommendations.

Change verification fails before archiving when the implementation does not fulfill the associated artifacts. The verification process highlights gaps and divergences between the code, tests, and design outputs against the delta specs.