Skill

Skill: risk-register

Build and maintain a structured delivery risk register with probability, impact ratings, mitigation plans, and ownership.

Install

npx claudepluginhub devmuslim/pdm-skills --plugin pdm-release-planning

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Build and maintain a structured delivery risk register with probability, impact ratings, mitigation plans, and ownership.

SKILL.md

Similar Skills

ui-ux-pro-max

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

57.6k

context7-mcp

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

51.8k

startup-financial-modeling

Builds 3-5 year financial models for startups with cohort revenue projections, cost structures, cash flow, headcount plans, burn rate, runway, and scenario analysis.

startup-business-analyst

32.9k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 9, 2026

Actions

View Source View Plugin View on GitHub View README

Skill: risk-register

Purpose

Build and maintain a structured delivery risk register with probability, impact ratings, mitigation plans, and ownership.

When to Use

At the start of release planning
After dependency mapping reveals new risks
During weekly delivery reviews

Framework: Delivery Risk Register

Step 1 — Risk Identification

Prompt the user to brainstorm risks across these categories:

Technical — Architecture unknowns, integrations, technical debt
Resource — Team availability, skill gaps, attrition
External — Vendor delays, third-party APIs, regulatory changes
Scope — Requirement changes, stakeholder misalignment
Timeline — Unrealistic estimates, holiday periods, dependencies
Quality — Test coverage gaps, insufficient UAT time

Step 2 — Risk Scoring

Rate each risk:

Probability: Low (1) / Medium (2) / High (3)
Impact: Low (1) / Medium (2) / High (3)
Score = Probability × Impact (1–9)

Step 3 — Risk Register Table

#	Risk Description	Category	Probability	Impact	Score	Status	Owner	Mitigation Plan	Contingency
R1	...	Technical	High	High	9	🔴 Open	...	...	...

Status icons:

🔴 Open — Active risk, not mitigated
🟡 Monitoring — Mitigation in progress
🟢 Closed — Risk resolved or no longer relevant

Step 4 — Risk Summary

Total risks by category
Top 3 risks requiring immediate action
Recommended escalations (Score 7–9 should go to steering committee)

Output Format

Risk register table (sorted by score descending)
Risk summary and top priorities
Escalation recommendations
Suggested next command: /assess-readiness or /plan-release