testland/risk-coverage-mapper
Build-an-X workflow that produces a risk-to-test-coverage matrix - maps each risk in the product/release register to the tests / cases / monitoring that mitigate it. Walks the author through ingesting risks (from risk-matrix / product-risk-register-builder), inventorying test coverage (test cases via traceability-matrix-builder, automated tests via repo scan, production monitoring via observability dashboards), and computing per-risk coverage depth + identifying orphan risks (no coverage) + orphan tests (not linked to risks). Output is a Markdown matrix + executive summary. Use before a release sign-off or compliance audit, when the team must show which tests, cases, or monitors back each registered risk and which risks have nothing behind them.
79
99%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
risk-coverage-output-templates.mdreferences/
Risk coverage output templates
Deep reference for the risk-coverage-mapper SKILL.md. The two reusable output formats the workflow emits - the per-risk coverage matrix (Step 4) and the executive summary (Step 6). Copy these skeletons; the worked example in SKILL.md shows them filled for one release.
Coverage matrix (Step 4)
One row per risk, ordered by score descending. An orphan risk (depth 0) is bolded and repeated in its own section so it cannot be missed.
# Risk coverage matrix - <release / quarter> - YYYY-MM-DD
**Total risks (score >= 5):** <n>
**Covered:** <n> (<%>)
**Orphan risks (no coverage):** <n> - <critical count> critical, <low count> low
**Average coverage depth:** <x.x>
## Risks by coverage
| Risk ID | Risk | Score | Automated tests | Manual cases | Monitors | Depth |
|---|---|---:|---|---|---|---:|
| <ID> | <title> | <score> | <test paths> | <case IDs> | <monitor IDs> | <n> |
| **<ID>** | **<title>** | **<score>** | ** - (ORPHAN)** | - | - | **0** |
## Orphan risks (critical action)
| Risk ID | Risk | Score | Why orphan |
|---|---|---:|---|
| <ID> | <title> | <score> | <reason: new risk, infra missing, ...> |
## Over-covered risks (audit)
| Risk ID | Risk | Depth |
|---|---|---:|
| <ID> | <title> | <depth 5+> |Executive summary (Step 6)
The stakeholder-facing rollup: a one-line headline, then the critical orphans (each with a recommended action, owner, and estimate), the audit list, and a coverage-debt trend table.
## Risk-coverage executive summary - <quarter>
### Headline
<n> of <n> medium-or-higher risks covered (<%>). <n> orphan risks require action before release.
### Critical orphans (must address before release)
- **<ID>** (score <n>): <title>. Recommended action: <tests/monitors> (<estimate>, owner <name>).
### Possibly over-covered (audit)
- **<ID>** (depth <n>): <title>. Audit the sprint for redundancy.
### Coverage debt trend
| Month | Orphan risks | Avg depth |
|---|---:|---:|
| <YYYY-MM> | <n> | <x.x> |Keep both artifacts version-controlled next to the matrix, so the trend table is real history rather than a re-estimate each cycle.