quality-risk-analysis
Use this skill when you need to identify and prioritize quality risks from product, change, and evidence inputs; triggers include quality risk analysis.
SKILL.mdskills/en/testing-types/quality-risk-analysis/SKILL.md
GitHubQuality Risk Analysis
When to Use
- Use this skill when you need to identify quality risks and prioritize them by likelihood, impact, detectability, and evidence.
- Use it to review an existing plan, result, or evidence set and produce actionable improvements.
- Use it when context is incomplete but a bounded first pass is still valuable.
Output Format Options
- Default to Markdown for review, execution, and incremental refinement.
- When the user requests tables, CSV, JSON, or ticket fields, preserve risk, evidence, priority, and boundary information.
- For machine-consumed output, confirm the schema, enums, and required fields first.
How to Use
- Read and follow
prompts/quality-risk-analysis.md, including its input contract, execution rules, minimum coverage, and output order. - Add only context that changes the decision: scope, environment, version, constraints, evidence, and success criteria.
- Audit the input, then separate confirmed facts, working assumptions, and open questions.
- Rank by risk and evidence strength, and produce an artifact that can be executed or reviewed directly.
- If information is missing, deliver a bounded first pass and state which conclusions remain unsupported.
Reference Files
When calibrating domain outcomes, valid controls, or evidence gaps, read references/domain-decision-example.md for sanitized input, per-item oracles, and reproducible calculations.
Always read
prompts/quality-risk-analysis.md; it is the complete execution specification for this skill.For evaluation or regression, read
evals/eval.yamland the relevant cases underevals/cases/.Load
references/,examples/,scripts/, oroutput-formats.mdonly when those directories exist and the task needs them.
Domain Execution Essentials
- Register risk events, affected assets/groups, triggers and controls with observable impact, likelihood and detectability anchors and sources.
- Without project quantitative rules provide justified qualitative ordering. Separate irreversible impact, authority boundaries and known control gaps; low frequency alone is not low risk.
- Propagate uncertainty across likelihood, impact and control confidence using conditional conclusions and minimal checks. UNKNOWN is neither zero nor a precise score.
- Link controls/tests, residual risk, owners and authorized acceptance. Ranking supports decisions; it is no vulnerability, root-cause or acceptance proof.
Core Constraints
- attach evidence and assumptions to scores
- avoid false precision
- explicitly accept or mitigate risks testing cannot remove
- Never invent system behavior, fields, data, metrics, or root causes absent from the evidence.
- Link important conclusions to evidence; mark unsupported conclusions as hypotheses with a verification method.
- Explain priority using business impact, likelihood, or detectability.
Delivery Checklist
- Covered: business criticality, failure modes, likelihood, impact, detectability, exposure window, existing controls, residual risk.
- Separated facts, assumptions, gaps, and recommendations.
- Gave high-risk items a priority, evidence basis, owner or next action.
- Defined verifiable decision criteria instead of generic advice.
- Performed no unauthorized production writes or destructive actions.
Common Pitfalls
- Listing checks without preconditions, expected outcomes, or evidence.
- Marking everything high priority and avoiding tradeoffs.
- Substituting tool names or generic theory for domain reasoning.
- Refusing incomplete input, or pretending incomplete evidence supports certainty.
Best Practices
- Start with paths most likely to cause business loss, safety issues, or release blockage.
- Reduce uncertainty through the smallest verifiable experiment and record reproduction conditions.
- Make the artifact executable and independently reviewable by another engineer.