openspec-verify-change

To verify implementation against specs before archiving, you validate task completion, requirement coverage, scenario tests, and design adherence using openspec CLI outputs and context files to generate a completeness, correctness, and coherence scorecard.

Implementation verification checks for missing or inconsistent work by mapping requirements to code, evaluating completeness, correctness, and coherence to ensure the implementation matches specs, tasks, and design artifacts.

Yes, you can validate task completion with partial artifacts like tasks-only or tasks and specs. The verification process works with graceful degradation, explicitly noting any skipped checks when full artifacts are unavailable.

To check requirement coverage and design adherence, apply verification to changes managed with openspec by reading CLI status and instructions outputs to locate specs, tasks, and context files, producing a prioritized report.

The best way to identify missing or inconsistent work before archiving is producing a structured report that evaluates completeness, correctness, and coherence, prioritizing findings as CRITICAL, WARNING, or SUGGESTION with specific remediation guidance.

Yes, you need openspec CLI outputs including list, status, and instructions apply, along with project context files and the ability to read artifacts to map requirements to code and generate the verification scorecard.