What problem does it solve? It closes the gap between claimed implementation and proven implementation in spec-driven development by requiring real test execution evidence before a change can be marked complete. ## Core Features & Use Cases - Runtime Verification: Executes test, build, and coverage commands and records exit codes and output hashes as evidence. - Spec Compliance Matrix: Maps every spec requirement and scenario to a covering test with COMPLIANT, FAILING, UNTESTED, or PARTIAL status. - Strict TDD Auditing: Optionally validates TDD cycle evidence, test layer distribution, changed-file coverage, and assertion quality when Strict TDD mode is active. - Use Case: After an apply phase finishes a change, the orchestrator delegates to this skill to run the test suite, compare results against specs and design, and produce a PASS, PASS WITH WARNINGS, or FAIL verdict report. ## Quick Start Ask the orchestrator to run the SDD verification phase for the current change and return the verification report with its final verdict.