openspec-verify-change

To validate code changes against design specs and tasks, compare the implementation with OpenSpec change artifacts. This enforces completeness and coherence checks, returning a structured report with actionable recommendations for any gaps.

OpenSpec change verification is the process of validating that an implementation matches change artifacts across codebases. It enforces completeness, correctness, and coherence checks to ensure code changes align with specifications, tasks, and design artifacts.

Generate a verification report for OpenSpec-driven changes by providing the change name and running the validation process. This compares specs, tasks, and design artifacts against code changes to guide archiving decisions with actionable recommendations.

Yes, you can check if your implementation matches specs, tasks, and design artifacts by running validation checks. This enforces correctness and coherence, producing a structured report that highlights any divergences between the code and artifacts.

When code changes diverge from change artifacts, review the structured verification report generated by the validation process. This report provides actionable recommendations to guide archiving decisions and address any gaps or divergences found.

Yes, you need OpenSpec change artifacts including specs, tasks, and design artifacts to validate code completeness. The verification process compares these artifacts against the implementation to enforce completeness, correctness, and coherence checks.