What problem does it solve? Product requirement documents describe boundaries and invariants in prose, leaving QA engineers to guess which guarantees are testable, which surfaces exist, and what oracle to assert against. This Skill turns a scenario document into concrete, prioritized test claims grounded in seeded fixtures and actual API routes. ## Core Features & Use Cases - Claim design from product docs: Maps personas (EXEC/LEAD/IC/ADMIN) to seeded fixtures, checks whether each surface exists, and emits claims with an oracle, layer (API vs UI), and blast-radius priority (P0/P1/P2). - Coverage triage: Records surface verdicts (Built/Partial/No surface/Not enforceable here), attributes existing tests to product clauses, and tracks issued claim IDs in SCENARIO-COVERAGE.md. - Findings capture: Surfaces divergences between the product document and the implementation, such as two group-size thresholds disagreeing on the number. - Use Case: Ask which product rules for scenario S-9 are unverified, and receive designed claims like "a lead asking for their own manager's subchart is refused, 404 not 403" with the oracle, route, priority, and confidence tag ready for test implementation. ## Quick Start Ask the assistant to design testable claims for scenario S-9 from the product scenarios document, grounded in the seeded roster.
