openspec-verify-change

You can verify code against change artifacts by loading specs, tasks, and design documents to check status and generate a verification report. This ensures completeness, correctness, and coherence by validating task completion, spec coverage, and design adherence.

Change artifact validation is the process of confirming an implementation matches its delta specs, tasks, and design before archiving. It generates a report with actionable recommendations to close gaps in specification coverage and design coherence.

You check implementation matches by loading design artifacts and running a verification workflow that assesses task completion, spec coverage, and code-pattern consistency. This generates a report with actionable recommendations to close any coherence gaps.

Yes, the openspec workflow supports spec coverage checks by validating alignment between code changes and delta specs. It loads artifacts, checks status, and builds a verification report highlighting gaps in specification coverage and task completion.

A limitation of verifying code against change artifacts is the dependency on having existing delta specs, tasks, and design documents. Without these artifacts loaded via the openspec workflow, the verification cannot assess completeness or generate actionable recommendations.