What problem does it solve? When a spec defines a scenario table (happy paths, errors, boundaries, adversarial cases), it is easy for tests to silently miss scenarios. This Skill heuristically matches test cases against each scenario row and reports coverage gaps before code ships. ## Core Features & Use Cases - Heuristic Scenario Matching: Matches tests to scenarios by precondition, trigger, and expected outcome similarity rather than mechanical name traceability, accepting property-based tests as covering multiple boundary or combinatorial scenarios. - Prioritized Findings: Flags fully uncovered scenarios as P1 SCENARIO_GAP findings and partially covered ones (trigger tested but outcome not asserted) as P2 PARTIAL findings. - Coverage Summary: Reports an X/Y scenarios covered percentage and routes uncovered security or boundary scenarios to the appropriate reviewer teammates via SendMessage. - Use Case: During a review phase on a diff over 100 lines, spawn this reviewer to read the epic's scenario table with bd show <epic>, scan the changed test files, and surface any S-IDs lacking test coverage. ## Quick Start Ask the agent to review the current diff's test files against the scenario table in the beads epic and report any uncovered or partially covered scenarios.
