When is the best time to use the Risk Profile skill?

The optimal time is pre-implementation, after a task specification is created but before coding begins, to allow risks to be designed out of the solution rather than retrofitted later.

How does this skill help with testing?

It automatically maps risks to test priorities: P0 (Critical) for scores ≥7, P1 (High) for scores 5-6, and P2 (Medium) for scores 3-4, ensuring your testing effort is concentrated where it matters most.

How does the P×I scoring methodology work?

It multiplies Probability (1-3) by Impact (1-3) to create a score from 1 to 9. Scores of 7 or higher are considered critical, while scores of 6 require active mitigation strategies.

Risk Profile Assessment

Name: Risk Profile Assessment
Author: adolfoaranaes12

byadolfoaranaes12

•

セキュリティとテスト

Assesses implementation risks using P×I scoring to prioritize test scenarios and inform quality gates.

概要

The Risk Profile Assessment skill provides a systematic framework for identifying and quantifying technical and operational risks before implementation begins. By evaluating potential issues across six critical dimensions—Technical, Security, Performance, Data, Business, and Operational—it generates a structured risk matrix that helps developers prioritize testing efforts (P0-P2) and develop robust mitigation strategies for high-impact items. This skill acts as an essential quality guardrail, predicting quality gate status and ensuring that complex features, external integrations, or data migrations are handled with foresight and comprehensive validation.

主な機能

Probability × Impact (P×I) scoring methodology for objective risk measurement
Quality gate impact prediction to identify potential blockers early in the development cycle
1 GitHub stars
Comprehensive assessment across 6 categories: Technical, Security, Performance, Data, Business, and Operational
Automated test prioritization (P0/P1/P2) based on risk severity scores
Actionable mitigation strategy development for all high-risk items (score ≥6)

ユースケース

Evaluating risks for complex features or external API integrations before starting the implementation phase
Prioritizing QA and automated test scenarios to ensure high-risk areas receive the most rigorous validation
Informing quality gate decisions during the final review phase to ensure all critical risks are addressed

概要

主な機能

Probability × Impact (P×I) scoring methodology for objective risk measurement
Quality gate impact prediction to identify potential blockers early in the development cycle
1 GitHub stars
Comprehensive assessment across 6 categories: Technical, Security, Performance, Data, Business, and Operational
Automated test prioritization (P0/P1/P2) based on risk severity scores
Actionable mitigation strategy development for all high-risk items (score ≥6)

ユースケース

Evaluating risks for complex features or external API integrations before starting the implementation phase
Prioritizing QA and automated test scenarios to ensure high-risk areas receive the most rigorous validation
Informing quality gate decisions during the final review phase to ensure all critical risks are addressed