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.
Install
npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/quality-risk-analysis
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install naodeng-awesome-qa-skills@llmmart
git clone https://github.com/naodeng/awesome-qa-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole naodeng/awesome-qa-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Quality 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.
Files (awesome-qa-skills)
-
agents
-
openai.yaml 295 B
Loading…
-
-
evals
-
cases
-
basic-success.yaml 868 B
Loading… -
domain-method-regression.yaml 1.6 KB
Loading… -
edge-incomplete-input.yaml 909 B
Loading… -
edge-risk-priority.yaml 868 B
Loading… -
phase-1-project-context.yaml 4.1 KB
Loading…
-
-
fixtures
-
check-domain-decisions.sh 95 B
Loading… -
check_domain_decisions.py 3.8 KB
Loading… -
domain-oracle.json 185 B
Loading…
-
-
eval.yaml 652 B
Loading…
-
-
prompts
-
quality-risk-analysis.md 4.7 KB
Loading…
-
-
references
-
domain-decision-example.md 1.6 KB
Loading…
-
-
SKILL.md 4.4 KB
--- name: quality-risk-analysis description: Use this skill when you need to identify and prioritize quality risks from product, change, and evidence inputs; triggers include quality risk analysis. license: PolyForm-Noncommercial-1.0.0 metadata: version: "1.0.0" compatibility: "" author: "Awesome QA Skills contributors" language: "en" category: "testing-types" source: "https://github.com/naodeng/awesome-qa-skills" license-url: "https://polyformproject.org/licenses/noncommercial/1.0.0" --- # Quality 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 1. Read and follow `prompts/quality-risk-analysis.md`, including its input contract, execution rules, minimum coverage, and output order. 2. Add only context that changes the decision: scope, environment, version, constraints, evidence, and success criteria. 3. Audit the input, then separate confirmed facts, working assumptions, and open questions. 4. Rank by risk and evidence strength, and produce an artifact that can be executed or reviewed directly. 5. 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](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.yaml` and the relevant cases under `evals/cases/`. - Load `references/`, `examples/`, `scripts/`, or `output-formats.md` only when those directories exist and the task needs them. ## Domain Execution Essentials 1. Register risk events, affected assets/groups, triggers and controls with observable impact, likelihood and detectability anchors and sources. 2. Without project quantitative rules provide justified qualitative ordering. Separate irreversible impact, authority boundaries and known control gaps; low frequency alone is not low risk. 3. Propagate uncertainty across likelihood, impact and control confidence using conditional conclusions and minimal checks. UNKNOWN is neither zero nor a precise score. 4. 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.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.