openspec-verify-change

Spec verification for change management assesses whether your implementation satisfies OpenSpec tasks, delta specs, and design decisions. It performs static evidence checks to detect divergences between requirement intent and code, ensuring coherence before archiving.

Requirements traceability in spec-driven development tracks whether each requirement and scenario in a change artifact has corresponding code evidence and test coverage. It ensures that implementation changes match the intended design decisions and spec deltas completely before archiving.

You check test coverage by scanning the implementation for scenario evidence and verifying that all task checkboxes in the change artifacts are complete. The verification process then outputs a prioritized markdown report highlighting critical coverage gaps and warnings before archiving.

Yes, static evidence checks can detect potential divergence between requirement intent and code evidence by analyzing delta spec files and design documents. This correctness and coherence check identifies mismatches and generates actionable recommendations with critical, warning, and suggestion priorities.

Yes, you need OpenSpec installed because the verification process applies OpenSpec instructions to load change artifacts, parse tasks, and scan for requirement evidence. The dependency is required to select unambiguous changes and generate the completeness assessment.

Automated spec verification relies on static evidence checks and parsed task checkboxes, meaning it may not fully evaluate complex runtime behaviors or subjective design coherence. It outputs warnings and suggestions but requires human review to confirm the final archiving decision for nuanced changes.