What problem does it solve? In document-driven development, requirements, designs, tests, and code drift apart silently. This Skill audits that drift before it ships: it checks whether requirement documents match the original ask, whether code actually satisfies acceptance criteria, whether UI implementations match design mockups, and whether task breakdowns are ready for development. ## Core Features & Use Cases - Four verification dimensions: --docs checks three-layer document alignment (original requirements → requirements doc → design → test cases); --impl verifies AC satisfaction, design conformance, and traceability against current code; --ui compares design mockups with implementation screenshots; --readiness gates task documents before development starts. - P1/P2/P3 severity grading: Every finding is classified with a fix route pointing to the responsible skill (e.g., missing tests route to /test-cases). - Structured reports: Generates verify-report.md or readiness-report.md with coverage matrices, issue summaries, and a plain-language "what you need to know" section. - Use Case: After finishing a feature's code, run /verify --impl to confirm each acceptance criterion is semantically satisfied by current code (not just old diffs), then proceed to adversarial review only if no P1 blockers exist. ## Quick Start Ask the AI to run /verify --impl on the completed tasks to check whether the code satisfies all acceptance criteria and matches the system design.
