What problem does it solve? Before archiving a change, teams need confidence that the implementation actually matches the planned specs, tasks, and design decisions. Manually cross-checking code against change artifacts is error-prone and often skipped, leading to incomplete or divergent implementations being archived. ## Core Features & Use Cases - Three-Dimension Verification: Checks Completeness (task checkboxes, spec coverage), Correctness (requirement implementation, scenario coverage), and Coherence (design adherence, code pattern consistency). - Prioritized Issue Reporting: Generates a structured report grouping findings into CRITICAL, WARNING, and SUGGESTION levels, each with actionable recommendations and file references. - Graceful Degradation: Adapts verification depth based on available artifacts, verifying only tasks when specs or design docs are missing. - Use Case: After finishing a feature tracked by an OpenSpec change, run verification to confirm all tasks are checked off, every requirement has corresponding code, and the implementation follows the design before archiving the change. ## Quick Start Verify that my current change implementation is complete and ready to archive.
