openspec-verify-change

You can verify implementations against design specs by loading change artifacts, checking task alignment, assessing scenario coverage, and generating a structured report with remediation recommendations to ensure completeness before archiving.

Change artifact verification is the process of validating that code, tests, and design align with delta specs and tasks, ensuring implementation completeness and coherence before a change is archived.

Checking alignment involves loading delta specs and tasks, mapping requirements to your implementation, checking design adherence, and generating a structured report that identifies any gaps with file references.

Yes, automated verification assesses scenario coverage by loading change artifacts, mapping requirements, checking design adherence, and producing a structured report that evaluates completeness and coherence across all defined scenarios.

Generating actionable remediation reports is best achieved by running a verification workflow that loads change artifacts, identifies gaps in code and tests, and outputs concrete recommendations with file references and a final assessment.

You should avoid automated design adherence checks when your changes are not tracked by the openspec workflow, as the verification process requires loading specific change artifacts like specs, tasks, and design documents to function properly.