What problem does it solve? It closes the gap between "code was written" and "code provably works" by acting as an independent quality gate that runs real tests and checks implementation against spec-driven development artifacts before a change is accepted. ## Core Features & Use Cases - Runtime Verification: Executes test, build, and coverage commands and records exit codes and output hashes as evidence, since static analysis alone never counts as verification. - Spec Compliance Matrix: Maps every requirement and scenario from specs to a covering test with statuses like COMPLIANT, FAILING, UNTESTED, or PARTIAL. - Strict TDD Auditing: When Strict TDD mode is active, validates the RED-GREEN-REFACTOR evidence from the apply phase and audits assertion quality to catch tautologies, ghost loops, and smoke-test-only checks. - Use Case: After an SDD apply phase finishes all tasks for a change, the orchestrator delegates to this skill, which runs the test suite, builds a compliance matrix, and returns a verdict of PASS, PASS WITH WARNINGS, or FAIL with issues grouped by severity. ## Quick Start Ask the orchestrator to run the SDD verification phase for the current change so it executes the tests and produces a verification report with a final verdict.
