openspec-verify-change

To verify change implementation before archiving, parse tasks.md and delta specs via openspec CLI to evaluate completeness, correctness, and coherence. This ensures implementation matches declared change intent and prevents prematurely archiving incomplete code changes.

Validating openspec tasks and delta specs requires running openspec CLI status and instructions commands to load change context. The process parses context files and produces a prioritized report with CRITICAL, WARNING, and SUGGESTION items for actionable fixes.

Openspec change verification works by applying artifact-driven checks to code review workflows, loading change context and evaluating design notes and tests. It avoids guessing ambiguous contexts by guiding users to select an explicit change before generating a completeness report.

Yes, spec-validation checks require an explicit change selected from openspec to avoid guessing ambiguous contexts. Selecting a specific change ensures the verification process accurately loads the correct tasks.md, delta specs, and design notes for evaluation.

A coherence and completeness report for change management includes prioritized CRITICAL, WARNING, and SUGGESTION items with specific file and line recommendations. This actionable output helps teams fix implementation gaps before archiving the verified change.

Your openspec verification report shows missing context files when implementation artifacts do not match declared change intent. The verification process parses tasks.md and delta specs to detect incomplete or incorrect artifacts, flagging them as CRITICAL or WARNING items.