create-a-simple-risk-register
Create a simple risk register with cause, event, consequence, likelihood, impact, controls, actions, ownership, and review dates. Use when a project or team needs a shared view of uncertain threats and opportunities.
来源信息
- 仓库
- protosphinx/sphinxstack
- 最近来源活动
- 2026年7月29日 13:55
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 3
- Forks
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
2 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- create-a-simple-risk-register
- category
- start
- description
- Create a simple risk register with cause, event, consequence, likelihood, impact, controls, actions, ownership, and review dates. Use when a project or team needs a shared view of uncertain threats and opportunities.
# create-a-simple-risk-register
Write risks as uncertain events, not current issues or vague concerns.
## When to use
- Use at project start, before a decision, or during recurring review.
- Do not hide severe risks inside an average score.
## Procedure
1. Define scope, objectives, time horizon, rating scale, review cadence, and escalation threshold.
2. Gather risks from plans, assumptions, dependencies, incidents, stakeholders, and subject experts.
3. Write each as cause, uncertain event, and consequence.
4. Record category, trigger, likelihood, impact, proximity, affected objective, existing controls, and evidence.
5. Assign owner, response, action, due date, residual rating, and contingency.
6. Separate active issues from risks and link them where related.
7. Review changed ratings, overdue actions, new risks, retired risks, and material residual exposure.
## Done
- A risk register lists identifiers, statements, ratings, controls, triggers, responses, owners, actions, dates, and status
- Scope, duplicate, issue, severity, owner, overdue-action, and escalation checks verify the register supports decisions
在 GitHub 查看