# project-risk-register

project-risk-register — a skill for identifying, assessing, and prioritizing project risks using probability-impact scoring. Assigns owners and mitigation plans, then tracks risk evolution throughout the project lifecycle.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 108 installs · ★ 203 repo stars
- Author: lyndonkl
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/lyndonkl/claude/tree/HEAD/skills/project-risk-register/SKILL.md
- Updated: 2026-09-01
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/project-risk-register

## What it does

The skill structures risk analysis through a 5×5 matrix: each risk receives a probability score (1–5) and impact score (1–5), multiplied together and plotted on a grid. Critical risks (≥20) require immediate action and weekly review; high risks (12–19) demand active management; medium risks (6–11) need close monitoring with monthly updates; low risks (1–5) can be accepted or minimally addressed.

For significant risks, a named owner is assigned, along with a mitigation plan (how to reduce probability beforehand), a contingency plan (what to do if the risk occurs), and triggers (when to activate the contingency). The skill suggests brainstorming categories: technical failures, schedule delays, resource gaps, external factors, and scope creep. Each risk type maps to response strategies—mitigate the probability, prepare a backup, transfer the risk, or accept it.

The register is reviewed weekly on active projects or monthly on longer ones. Probabilities and impacts shift as the project context changes. Watch for increasing scores over time—a red flag that mitigation is failing or new problems are emerging faster than they're resolved.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add lyndonkl/claude --skill project-risk-register -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/project-risk-register/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/project-risk-register/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add lyndonkl/claude --skill project-risk-register -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/project-risk-register/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add lyndonkl/claude --skill project-risk-register -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/project-risk-register/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install lyndonkl/claude skills/project-risk-register
```

2. **Manually: put the files in place**
- File: `.github/skills/project-risk-register/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add lyndonkl/claude --skill project-risk-register -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/lyndonkl/claude --path skills/project-risk-register
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/project-risk-register/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add lyndonkl/claude --skill project-risk-register -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/lyndonkl/claude/tree/HEAD/skills/project-risk-register/SKILL.md

## When to use it
- build a risk register and visualize risks on a probability-impact matrix
- assess and score each risk for prioritization
- identify which risks require immediate escalation
- assign owners, mitigation strategies, and contingency plans
- monitor and update risk status throughout the project

## Example prompts
- What risks could derail our data migration project?
- Help me build a risk register for this product launch
- Plot these risks on a probability-impact matrix and flag the critical ones

## Similar
- [risk-register](https://affpapa.org/en/nevibecode/skills/risk-register.md) — skill · ★ 1627 repo stars
- [project-manager](https://affpapa.org/en/nevibecode/skills/project-manager.md) — skill · ★ 117 repo stars
- [project-artifact](https://affpapa.org/en/nevibecode/skills/project-artifact.md) — skill · 2323 installs
- [milestone-review](https://affpapa.org/en/nevibecode/skills/milestone-review.md) — skill · 664 installs
- [risk-playbooks](https://affpapa.org/en/nevibecode/skills/risk-playbooks.md) — skill · ★ 450 repo stars
- [risk-management](https://affpapa.org/en/nevibecode/skills/risk-management.md) — skill · 2100 installs

From the same set: [lyndonkl/claude](https://affpapa.org/en/nevibecode/by/lyndonkl/claude.md) — 49 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
