openspec-verify-change

Verify implementation against change specs by cross-checking delta artifacts, tasks, and design notes to ensure completeness and coherence. The process generates a structured verification report with prioritized CRITICAL, WARNING, and SUGGESTION findings plus concrete file references.

OpenSpec change validation is a structured process checking that implementations match delta specs, tasks, and design artifacts. You need it before archiving changes to enforce completeness, correctness, and coherence across your codebase and specification cross-references.

Generate a verification report by providing the change name to validate against its delta specs. The process checks artifact presence, status, and cross-references to specs and scenarios, outputting a report with actionable recommendations and file references.

Yes, you can validate implementation correctness and coherence with no external dependencies. The verification process applies OpenSpec-based checks internally to cross-reference implementations against delta specs, tasks, and design notes, producing actionable findings autonomously.

CRITICAL findings indicate severe completeness or correctness gaps blocking archival, while WARNING findings highlight coherence issues between implementation and delta specs. SUGGESTION findings offer improvement recommendations. Each includes concrete file references for targeted resolution.

Avoid automated spec validation when delta artifacts like specs, tasks, or design notes are missing or incomplete. The verification process requires defined change artifacts to cross-reference; without them, it cannot assess implementation completeness, correctness, or coherence meaningfully.