openspec-verify-change

To verify code changes against delta specs before archiving, load the change context using OpenSpec commands to map implementation to requirements and generate an actionable verification report.

Change verification in spec-driven workflows identifies whether an implementation aligns with its delta specs, tasks, and design artifacts, ensuring requirements are fully implemented before archiving.

You can detect missing requirements and surface divergences by fetching change status and loading artifacts via OpenSpec commands, which validates code coherence and highlights incomplete implementations.

Yes, you can use OpenSpec to generate an actionable verification report by running status and instruction commands to load change context, surfacing divergences and providing corrective recommendations.

The best way to ensure spec traceability before archiving is to verify the mapping between delta specs and code changes, confirms implementation completeness, and surfaces any architectural divergences.