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.

Informações da origem

Repositório
protosphinx/sphinxstack
Última atividade na origem
29 de julho de 2026 às 13:55
Idioma detectado do SKILL.md
inglês
Estrelas
3
Forks
0

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos
2 arquivos

Exibindo SKILL.md

SKILL.md
Instruções da origem · Visualização somente leitura
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 no GitHub