What problem does it solve? Before writing tests, reviewing a diff, or gating a release, teams often guess at which checks a change actually needs. This Skill produces a structured QA and review plan that maps risk areas to the right test levels and review lenses, states what is not needed and why, and defines the evidence required to close the change. ## Core Features & Use Cases - Risk-to-check mapping: Identifies risk areas (behavior, persistence, security, performance, docs contract, release authority, end-user workflows) and matches each to checks such as unit, integration, failure-injection, contract-drift, and fresh-context review. - Cost-aware recommendations: Assigns each recommended check a cost (cheap, moderate, expensive) and requires justification for expensive ones. - Explicit exclusions and handoff: States which checks are unnecessary and why, then names which skill or review lens runs next and the evidence each must return. - Use Case: Before implementing a change to a shared dashboard frontend, use this Skill to produce a plan requiring smoke tests of all dashboard views, security review only if input surfaces change, and a planning-artifact evidence record for close. ## Quick Start Ask the agent to plan the QA strategy for your proposed change, listing the risk areas, required tests and review lenses, what can be skipped, and the evidence needed for close.
