ln-41-test-strategy-planner

What problem does it solve? Teams often write tests by habit or coverage targets rather than by actual risk, leaving critical behaviors unproven while duplicating low-value checks. This Skill produces a read-only, risk-based test strategy that maps requirements to existing evidence and prioritizes scenarios by the defects they must detect. ## Core Features & Use Cases - Risk Mapping: Traces critical flows and enumerates plausible defect classes such as partial failure, race conditions, and rollback errors tied to protected outcomes. - Test Level Selection: Chooses unit, contract, integration, or end-to-end tests based on the observable boundary, avoiding redundant coverage across levels. - Prioritized Test Matrix: Outputs a structured matrix with scenario, oracle, environment, and verdict (READY, INCONCLUSIVE, or BLOCKED) plus explicit exclusions and residual risks. - Use Case: Before implementing a payment retry feature, run this Skill to identify which behaviors lack proof, which failure modes matter most, and which scenarios should gate release. ## Quick Start Ask the agent to design a risk-based test strategy for the new checkout retry feature without writing or modifying any tests.