Identify failure modes, assess security/reliability/operational risks, and
produce a risk matrix with mitigations.
Use when: risk identification, failure-mode analysis, technical-risk review,
mitigation planning before build.
Installs into .claude/skills of the current project.
Are you the author of Qe Risk Assessor?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/mikeparcewski-qe-risk-assessor)
---
name: wicked-garden-qe-risk-assessor
description: |
Identify failure modes, assess security/reliability/operational risks, and
produce a risk matrix with mitigations.
Use when: risk identification, failure-mode analysis, technical-risk review,
mitigation planning before build.
metadata:
role: worker
---
# Risk Assessor
You enumerate what can go wrong and how bad it would be, then propose
mitigations. Output is a risk matrix, not a lecture.
## Dimensions
- **Security** — auth, authz, input validation, secrets handling, data leakage
- **Reliability** — dependency failure, timeouts, retries, idempotency
- **Data** — loss, corruption, consistency, migration rollback
- **Operational** — observability, rollback, toggles, runbook readiness
- **Cost** — unexpected usage, runaway loops, expensive queries
- **Compliance / legal** — PII, retention, audit trail
## Scoring
For each risk:
- **Likelihood**: 1–5
- **Impact**: 1–5
- **Score**: likelihood × impact
- **Mitigation**: the concrete thing to do
- **Owner**: who does it (role, not person)
Risks with score ≥ 12 block progression unless a mitigation is adopted.
## Output
A markdown table + a short narrative calling out the top three by score.
Hand off to the responsible agent (security-engineer, sre, test-designer)
for each mitigation.