Skip to main content

create-a-risk-register

Create an actionable risk register linking uncertain events to evidence, exposure, treatment, triggers, and ownership. Use when a project or operation needs explicit risk decisions.

Datos de origen

Repositorio
protosphinx/sphinxstack
Última actividad en el origen
29 de julio de 2026 a las 13:55
Idioma detectado de SKILL.md
inglés
Estrellas
3
Forks
0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos
2 archivos

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
create-a-risk-register
category
data
description
Create an actionable risk register linking uncertain events to evidence, exposure, treatment, triggers, and ownership. Use when a project or operation needs explicit risk decisions.
# create-a-risk-register Describe uncertain future events separately from active issues. Use the register to drive treatment and escalation, not to collect vague worries. ## Procedure 1. Confirm scope, objectives, time horizon, risk authority, review cadence, and impact categories. 2. Gather risks from plans, assumptions, dependencies, incidents, contracts, data, operators, and affected stakeholders. 3. Write each risk as cause, uncertain event, and consequence. 4. Link evidence, affected objective, exposure window, current controls, and control confidence. 5. Score likelihood and impact with defined scales; record uncertainty rather than false precision. 6. Assign one risk owner and a treatment choice: avoid, reduce, transfer, accept, investigate, or exploit. 7. Define actions, due dates, residual exposure, leading indicators, trigger thresholds, and contingency. 8. Escalate risks beyond tolerance to the authority that can accept or fund treatment. 9. Review changes, close expired risks with evidence, and convert realized risks into issues without deleting history. ## Failure plan - Do not label active defects or guaranteed commitments as risks. - Never reduce a material safety, legal, security, privacy, or financial exposure to a color without detail. - If scoring hides catastrophic low-frequency harm, show the impact explicitly. - Do not let an unowned treatment create the appearance of control. ## Done - Material risks have evidence, exposure, controls, owners, treatments, triggers, and contingencies - Acceptance and escalation match documented authority and tolerance - Review history, realized issues, and closed risks are traceable
Ver en GitHub