openspec-verify-change

To verify change artifacts align with specs and tasks, you can run a completeness and correctness assessment across delta specs. This process maps each requirement to code evidence and flags any divergences before archiving.

Checking completeness and coherence across delta specs involves validating that required specs exist, task completion statuses are met, and design decisions follow project standards. It surfaces gaps in correctness to ensure full alignment.

Mapping spec requirements to codebase evidence requires access to the codebase to search for implementation mappings and test coverage. This confirms that each requirement has corresponding code evidence and flags potential divergences.

Yes, you can verify change artifacts with only partial specs or tasks. The verification process applies graceful degradation, focusing on available checks like tasks.md and skipping unavailable ones while reporting missing artifacts.

Yes, you need the openspec CLI to check if change implementations are complete. It is required to prompt for available changes and search the codebase for implementation mappings and test coverage during the verification process.

The best way to surface gaps in correctness before archiving a change is to evaluate coherence against project standards and map requirements to code evidence. This identifies missing requirements or misaligned implementations prior to archiving.