skills.rest
qa-aman
qa-amanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

risk-register

Consolidates project risks into a centralized register with likelihood-impact scoring and mitigation tracking.

11|Updated Mar 20, 2026
Search Tags:#risk management#risk assessment#consolidation#mitigation#risk register#likelihood impact matrix#project risk
One-click install
npx skills add https://github.com/qa-aman/next-leap-claude-code --skill risk-register-qa-aman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: risk-register
Source: https://github.com/qa-aman/next-leap-claude-code/tree/main/.claude/skills/risk-register
Command: npx skills add https://github.com/qa-aman/next-leap-claude-code --skill risk-register-qa-aman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project risks are scattered across individual specs and PRDs, making it hard to see the full risk picture, track mitigations, or know which risks need immediate attention. This Skill consolidates them into one living register. ## Core Features & Use Cases - Risk Consolidation: Reads Risks and Assumptions sections from specs and merges them into a single register without duplicating entries. - Standardized Scoring: Applies a likelihood x impact matrix to assign Critical, High, Medium, or Low priority to every risk. - Governance Rules: Enforces owners, mitigation plans, sequential risk IDs, and review dates so the register stays actionable. - Use Case: Before a quarterly planning review, ask for a cross-project risk register to surface all Critical risks, overdue reviews, and risk trends across your product specs. ## Quick Start Ask the AI to build a risk register by consolidating the Risks and Assumptions sections from all specs in the project.

Frequently Asked Questions about risk-register

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a risk register from product specs?▼

Point the skill at your specs and it reads each Risks and Assumptions section, merges matching entries, scores them with a likelihood-impact matrix, and outputs a formatted register with owners, mitigations, and status.

How does the likelihood impact matrix assign risk priority?▼

Each risk is rated Low, Medium, or High on both likelihood and impact. The matrix maps combinations to priorities: High likelihood with High impact is Critical, while Low likelihood with Low impact is Low priority.

Can I merge new risks into an existing risk register?▼

Yes. The skill reads the existing register first and matches risks by description to avoid duplicates. Existing risk IDs are preserved, and only genuinely new risks receive the next sequential ID.

What is the difference between a risk and an assumption in the register?▼

Only risks go into the register; assumptions are explicitly excluded. A risk is a potential negative event with likelihood and impact, while an assumption is a belief taken as true and tracked separately.

Why does every risk need an owner and mitigation plan?▼

The skill enforces these as hard rules because a risk without an accountable owner or a mitigation plan cannot be acted on. Entries with TBD owners or empty mitigations are treated as anti-patterns and rejected.

Related Skills

Explore More Product & Management Skills→
Zeyad-37Zeyad-37

write-prd

Generates a structured Product Requirements Document with RICE scoring and approval workflow.

Community
Intermediate
gcamptongcampton

gteam-project-manager

Convert ambiguous project requirements into executable plans with scoped tasks, owners, and acceptance criteria.

Community
Advanced
jmaglyjmagly
175

risk-cycle

Track and manage risks across the Software Development Life Cycle.

Community
Intermediate
kortix-aikortix-ai

risk-assessment

Score legal risks in contracts using a Severity x Likelihood matrix.

Official
Advanced