What problem does it solve?
Teams often accumulate tests without a clear rationale, leaving critical risks unproved while low-value tests multiply. This Skill produces a read-only, risk-based test strategy that maps requirements to existing evidence and decides which tests to keep, add, update, merge, delete, or deliberately omit.
Core Features & Use Cases
- Risk Mapping: Traces critical flows and enumerates plausible defect classes tied to protected outcomes like money, authorization, and data integrity.
- Portfolio Decisions: Assigns every material risk an explicit action (KEEP, ADD, UPDATE, MERGE, DELETE, NO_TEST) with level, oracle, environment, and gate.
- Prioritized Test Matrix: Orders scenarios so safety-critical checks run first, separates release gates from diagnostics, and states exclusions and residual risks.
- Use Case: Before implementing a payment retry feature, run this Skill to identify which behaviors lack proof, decide the right test level for each risk, and produce a READY verdict with a prioritized scenario matrix.
Quick Start
Ask the agent to design a risk-based test strategy for the new checkout retry feature without writing or changing any tests.