What problem does it solve? Teams often mark development phases as complete based on claims in summary documents, only to discover later that code is stubbed, unwired, or missing. This Skill verifies implemented work against stated phase goals using empirical evidence instead of trusting completion claims. ## Core Features & Use Cases - Three-Level Artifact Verification: Checks that required files exist, contain substantive implementations (not stubs or placeholders), and are actually wired into the application. - Key Link and Wiring Validation: Confirms critical connections such as component-to-API calls, API-to-database queries, and form-to-handler bindings. - Structured Gap Reporting: Produces a VERIFICATION.md with status (passed, gaps_found, human_needed), a verification score, anti-pattern findings, and YAML-structured gaps consumable by planning workflows. - Use Case: After a coding agent finishes a chat feature phase, run verification to confirm Chat.tsx fetches from /api/chat, renders messages from state, and contains no TODO stubs before approving the phase. ## Quick Start Verify phase 3 of my project against its roadmap goal and generate a VERIFICATION.md report with any gaps found.
