openspec-verify-change

Spec-driven verification evaluates tasks, delta specs, and design notes against actual code artifacts before archiving. This structured review checks completeness, correctness, and coherence to ensure readiness for release while reducing missed requirements and regressions.

Spec-driven verification is a process that validates whether an implementation fully and correctly realizes change artifacts. It maps requirements and scenarios to code, ensuring design adherence and pattern consistency across three dimensions: completeness, correctness, and coherence, classified by CRITICAL, WARNING, or SUGGESTION findings.

You can check task completion by applying a completeness verification check to your change artifacts. This process inspects the tasks list, evaluates coverage against delta specs, and produces a structured report highlighting incomplete tasks, missing requirement implementations, or design divergences that must be fixed before archiving.

Yes, verification can gracefully degrade to support partial checks when only tasks or specs are available. The process explicitly reports any skipped checks with reasons, allowing you to proceed with available context files while surfacing missing requirement implementations or design divergences.

Yes, openspec verification supports partial checks when only tasks or specs are available, explicitly reporting skipped checks with reasons. This graceful degradation allows you to validate available change artifacts and surface design divergences without requiring all context files to be present.