What problem does it solve? Before archiving a change in an OpenSpec workflow, teams need confidence that the implementation actually matches the planned specs, tasks, and design decisions. Manually cross-checking code against change artifacts is slow and error-prone, and incomplete work can slip through. ## Core Features & Use Cases - Three-Dimension Verification: Audits completeness (task checkboxes, spec coverage), correctness (requirement implementation, scenario coverage), and coherence (design adherence, code pattern consistency). - Prioritized Issue Reporting: Generates a markdown report with a summary scorecard and issues grouped as CRITICAL, WARNING, or SUGGESTION, each with actionable recommendations and file references. - Graceful Degradation: Adapts verification depth based on available artifacts, verifying only tasks if specs or design documents 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 OpenSpec change implementation is complete and ready to archive.
