From magic-powers
Use when managing quality risk — identifying quality risks in a product or release, applying risk-based testing prioritization, creating risk mitigation plans, and communicating quality risk to stakeholders for go/no-go decisions.
npx claudepluginhub kienbui1995/magic-powers --plugin magic-powersThis skill uses the workspace's default tool permissions.
- Planning testing for a release with limited time/resources
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
## Quality Risk Register — v2.0 Release
| Risk ID | Risk Description | Area | Likelihood | Impact | Risk Level |
|---------|-----------------|------|-----------|--------|-----------|
| QR-01 | Payment flow regression due to refactor | Checkout | High | Critical | CRITICAL |
| QR-02 | Performance degradation from new DB queries | Search | Medium | High | HIGH |
| QR-03 | Third-party auth provider API changes | Login | Low | Critical | HIGH |
| QR-04 | Mobile layout broken on iOS 17 | UI | Medium | Medium | MEDIUM |
| QR-05 | Email notifications delayed | Notifications | Low | Low | LOW |
Risk Level = Likelihood x Impact:
CRITICAL: Likelihood High + Impact Critical/High
HIGH: Likelihood Medium + Impact Critical, OR High + High
MEDIUM: Medium x Medium combinations
LOW: Low likelihood or low impact
Given: 40 hours of testing available for v2.0 release
Risk-based allocation:
CRITICAL risks (QR-01): 16 hours (40%)
- Full regression of payment flow
- All payment methods tested
- Boundary testing on amounts
HIGH risks (QR-02, QR-03): 16 hours (40%)
- Performance test: search under load
- Auth provider integration smoke test
- Fallback behavior tested
MEDIUM risks (QR-04): 6 hours (15%)
- iOS 17 spot check on critical pages
LOW risks (QR-05): 2 hours (5%)
- Smoke test email delivery
Without risk-based approach:
- Equal time per feature = critical areas undertested
- QR-01 payment regression found in production
## Release v2.0 — Go/No-Go Risk Assessment
**Release Date:** 2026-04-15
**QA Lead:** [Name]
### Change Risk Summary
| Change | Risk Level | Test Coverage | Outstanding Issues |
|--------|-----------|--------------|-------------------|
| Payment refactor | CRITICAL | 95% | 0 P1, 1 P2 |
| Search optimization | HIGH | 82% | 0 P1, 2 P2 |
| Auth integration | HIGH | 78% | 0 P1, 0 P2 |
| Mobile layout | MEDIUM | 90% | 0 P1, 1 P3 |
### Risk Mitigation Status
OK QR-01: Payment regression fully tested, no issues found
OK QR-02: Performance tested — 12% improvement, no regressions
WARN QR-03: Auth provider test partially complete (3rd party sandbox down)
OK QR-04: iOS 17 tested on critical paths, minor P3 in settings
### Outstanding Risk Items
| Item | Risk | Mitigation |
|------|------|-----------|
| P2: Search slow on >10K results | MEDIUM | Feature flag: disable for enterprise |
| Auth provider untested | HIGH | Rollback plan ready; monitor after deploy |
### Recommendation
**CONDITIONAL GO** — deploy with:
1. Feature flag enabled for enterprise search (P2 mitigation)
2. Enhanced monitoring on auth service for 24h post-release
3. On-call engineer available for 4h after deployment
4. Rollback plan: revert auth config if error rate >1%
QA Sign-off: _________________ Date: _______
For each identified risk, choose a mitigation strategy:
AVOID — eliminate the risk entirely
"Don't release the payment refactor this sprint — too high risk before holiday sale"
MITIGATE — reduce likelihood or impact
"Add integration tests for the auth provider to reduce likelihood"
"Use feature flag to limit exposure if issues arise (reduce impact)"
TRANSFER — shift risk to someone else
"SLA with third-party provider covers downtime"
"Insurance for financial loss from payment failures"
ACCEPT — acknowledge risk and proceed
"Minor UI issue on iOS 17 — accept and fix in next sprint"
"Very low likelihood — monitoring in place, proceed"
Decision matrix:
CRITICAL risk + no mitigation -> DELAY release
HIGH risk + mitigation in place -> CONDITIONAL GO
MEDIUM risk + monitoring -> GO with observation
LOW risk -> GO, document for future
qa-process-design — quality process should include risk assessment stepqa-audit — audit findings generate new risks for the risk registerqc-metrics — historical defect data informs risk likelihood estimatestest-strategy — risk register directly drives test strategy prioritization