openspec-verify-change

To verify code changes match specs before archiving, compare the implementation against change artifacts like delta specs and tasks to check completion, correctness, and coherence. The process returns a structured report with spec coverage and actionable recommendations.

Change artifact verification is the process of cross-checking implemented code against delta specs, tasks, and design guidance to confirm completeness and correctness. It outputs a structured report detailing task completion, spec coverage, and design adherence.

Check implementation coverage by comparing the codebase against available change artifacts. The verification process analyzes task completion, spec coverage, and design adherence, returning a report with exact file references and actionable recommendations.

Yes, you can verify a code change with missing spec artifacts. The verification process gracefully handles incomplete artifact sets by focusing on what is available and clearly signaling gaps in the structured report for remediation.

Verification works for incomplete change artifacts by adapting to focus on available delta specs, tasks, or design guidance. It clearly signals missing artifacts in the returned report, ensuring gaps are identified for remediation.

The best way to ensure implementation aligns with design guidance is running a verification workflow against change artifacts. It confirms design adherence, task completion, and spec coverage, returning a structured report with exact file references.