Skip to main content

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
포크
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에서 보기