risk-based-testing

Generates a scored risk matrix and heatmap that maps test coverage to business impact and probability.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/100Thieves-team/plady-expert-skills --skill risk-based-testing-100thieves-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: risk-based-testing
Source: https://github.com/100Thieves-team/plady-expert-skills/tree/main/.claude/skills/risk-based-testing
Command: npx skills add https://github.com/100Thieves-team/plady-expert-skills --skill risk-based-testing-100thieves-team

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Equal test coverage across all features wastes effort on low-risk areas while leaving critical paths like checkout and authentication under-tested. This Skill quantifies risk as impact multiplied by probability, so testing effort goes where failures would hurt most. ## Core Features & Use Cases - Risk Scoring and Heatmap: Classifies every feature on 1-5 impact and probability scales, computes composite scores, and plots them on a 5x5 heatmap with CRITICAL, HIGH, MEDIUM, and LOW zones. - Failure Mode Analysis: For every item scoring 10 or above, documents trigger, blast radius, detection method, current mitigation, and gaps, including dedicated AI/LLM failure classes such as hallucination, prompt injection, and privacy leaks. - Coverage Alignment and Reassessment: Prescribes per-zone unit, integration, E2E, and monitoring targets, runs gap analysis against current coverage, and defines reassessment triggers after incidents, dependency changes, or quarterly reviews. - Use Case: Before writing a test plan for a new e-commerce release, run this Skill to discover that checkout scores 20 (CRITICAL) while the settings page scores 4 (LOW), then allocate 90% branch coverage and load tests to checkout instead of spreading effort evenly. ## Quick Start Ask the AI to build a risk matrix for your product by scoring each feature on impact and probability, then map test coverage to the resulting risk zones.

Frequently Asked Questions about risk-based-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a risk matrix for software testing?

Score each feature on impact (1-5) and probability (1-5), multiply them for a composite score, and plot results on a 5x5 heatmap. Scores of 15-25 are CRITICAL, 10-14 HIGH, 5-9 MEDIUM, and 1-4 LOW, each with prescribed test coverage actions.

What is risk-based testing and when should I use it?

Risk-based testing allocates test effort according to impact multiplied by probability instead of covering everything equally. Use it before writing a test strategy or sprint test plan, after production incidents, or when deciding where to focus limited QA capacity.

How do I assess risk for AI and LLM features?

Classify AI features against the CT-GenAI failure classes: hallucination, bias, prompt injection, privacy leak, and regulatory non-compliance. Score impact and probability independently, and treat an automated eval suite as the mitigation rather than a single manual test.

How does risk-based testing differ from a test strategy or test plan?

Risk assessment produces the scored matrix that feeds the other artifacts. A test strategy covers multi-quarter QA direction, a test plan covers a single sprint or release, and risk-based testing supplies the priority data both consume.

When should a risk matrix be updated?

Reassess within 48 hours of any production incident, when new features or dependencies are introduced, when team composition changes, and quarterly at minimum. Track code churn, defect clustering, and near-misses as continuous signals that the model has drifted.