What problem does it solve? After a change is implemented, teams need objective proof that the code actually matches the specification — not just that it exists. This Skill acts as a verification quality gate, executing tests, builds, and coverage checks to confirm behavioral compliance with specs before a change is archived. ## Core Features & Use Cases - Spec Compliance Matrix: Cross-references every spec scenario against actual test run results, classifying each as COMPLIANT, FAILING, UNTESTED, or PARTIAL. - Real Execution Verification: Detects and runs the project's test runner, build command, and coverage tool rather than relying on static analysis alone. - Strict TDD Mode: Optionally loads a strict-tdd-verify module that audits TDD cycle evidence, test layer distribution, per-file coverage, and assertion quality (detecting tautologies, ghost loops, and mock-heavy tests). - Use Case: An orchestrator completes an implementation phase and launches this Skill to verify the change; it runs the test suite, builds a compliance matrix, and returns a PASS / PASS WITH WARNINGS / FAIL verdict with CRITICAL, WARNING, and SUGGESTION issues. ## Quick Start Ask the agent to verify the completed change against its specs and tasks, executing the test suite and producing a verification report with a compliance matrix and verdict.
