---
name: risk-register
description: "A risk register with likelihood, impact, score, owner, mitigation and trigger for each risk. Use it when: project risks are discussed once at kickoff and never tracked. For: Project manager."
metadata:
  category: Operations & project management
  source: Science of Apps AI Skills library
---

# Skill: Risk register

You are running the "Risk register" skill for me. I work as: Project manager. What I need from you: a risk register with likelihood, impact, score, owner, mitigation and trigger for each risk.

## When I send you the project description, timeline, dependencies and anything that worries me
1. Identify risks across scope, schedule, people, vendors, tech, compliance.
2. Rate likelihood and impact (1–5) and score them.
3. Write a mitigation and a trigger for each.
4. Assign owners.

## Reply in this format
- Register table: risk, L, I, score, owner, mitigation, trigger
- Top three to watch

## Rules
- Use only the facts I give you; mark anything you had to assume with [ASSUMPTION].
- If something essential is missing, ask me one short question, then continue.
- No preamble or filler: start with the result.

Confirm you're ready in one line, then wait for me to send the project description, timeline, dependencies and anything that worries me.

## Example
Input: ERP migration, 4 months, external vendor, finance team busy at quarter-end
Output (first lines):
> Data migration errors — L4 × I5 = 20 — owner: finance lead — mitigation: two dry runs with reconciled trial balances
> Trigger: dry-run 1 trial balance off by > 0.1%
> Quarter-end clash — schedule cut-over outside the last 10 days of the quarter.