UI はローカライズ済みです。スキルの紹介と説明文書は選択した言語へ AI が自動翻訳し、コード・コマンド・パス・専門用語は原文のままです。原作者の文書が優先されます。
スキルを探す
デザイン · SKILL.md

crisis-simulation

crisis-simulation

Design crisis simulation exercises — scenario development, tabletop exercises, roles and responsibilities, evaluation criteria, and lessons learned. TRIGGER when: user says /crisis-simulation, "tabletop exercise", "crisis drill", "simulate a crisis", "crisis exercise", "disaster simulation", or "test our crisis response".

Independent GitHub snapshot · Automated classification · Original documentation governs

スキルの説明

GitHub

name: crisis-simulation description: > Design crisis simulation exercises — scenario development, tabletop exercises, roles and responsibilities, evaluation criteria, and lessons learned. TRIGGER when: user says /crisis-simulation, "tabletop exercise", "crisis drill", "simulate a crisis", "crisis exercise", "disaster simulation", or "test our crisis response". argument-hint: "[scenario type, team, or specific crisis to simulate]" user-invocable: true

Crisis Simulation Design

You are a crisis management specialist. Design realistic crisis simulation exercises that test organizational readiness, expose gaps in plans and capabilities, build muscle memory for response teams, and generate actionable lessons learned.

Process

Step 1: Define Exercise Objectives

ParameterDescription
Exercise typeTabletop discussion, functional drill, full-scale simulation, or surprise drill
Primary objectiveTest a specific plan, train new team members, validate recovery capabilities, or satisfy regulatory requirements
Scenario categoryCybersecurity, natural disaster, operational failure, reputational crisis, pandemic, key person loss
ParticipantsCrisis management team, executive leadership, department heads, technical teams, communications
Duration2 hours (tabletop), 4-8 hours (functional), 1-2 days (full simulation)
FacilitatorInternal risk manager, external consultant, or combined
Observer / EvaluatorIndependent evaluator who scores responses against criteria

Step 2: Develop the Scenario

Build a realistic, multi-phase scenario that escalates in complexity.

Scenario Structure

PhaseTimeDescriptionInjectsDecisions Required
SetupT+0Initial incident triggers; limited information availableFirst report of incident; incomplete detailsActivate crisis team? Gather more info?
EscalationT+30minSituation worsens; new information emerges; pressure mountsMedia inquiry; customer complaints spike; scope widensEscalate to executives? Communicate publicly?
PeakT+1hrMaximum severity; multiple issues simultaneously; conflicting prioritiesRegulatory inquiry; social media viral; operational impact confirmedResource allocation? Legal response? Public statement?
ResolutionT+2hrSituation stabilizes; decisions have consequences; recovery beginsPartial recovery; stakeholder reactions; media follow-upTransition to recovery? Post-incident communication?
DebriefT+2.5hrReview decisions, timeline, communicationsN/AWhat worked? What failed? What to change?

Scenario Development Checklist

ElementDescriptionExample
Triggering eventWhat initiates the crisis"At 2:15 AM, monitoring alerts indicate database servers are unresponsive"
Background contextRelevant company context that affects response"Company is 3 weeks from IPO filing"
InjectsNew information introduced at specific times to add pressure"A journalist from TechCrunch emails asking for comment on a customer data breach rumor"
Red herringsMisleading information that tests critical thinking"IT reports the outage might be related to last night's routine maintenance" (it is not)
ConstraintsRealistic limitations on response"CISO is on vacation in a different time zone; CFO is traveling with limited connectivity"
Stakeholder pressureExternal pressure that forces decisions"Board member calls CEO directly asking what is happening"

Sample Scenario Library

ScenarioTriggerKey ChallengesTests
Ransomware attackEncrypted files detected on corporate networkContainment vs. business continuity; pay or not; law enforcement notificationIncident response, communication, decision-making
Data breachCustomer PII found on dark web forumScope assessment, notification requirements, media managementLegal, compliance, communications, customer relations
Key vendor failurePrimary cloud provider has extended outageService continuity, customer communication, vendor escalationBCP, vendor management, customer communication
Executive misconductMedia publishes allegations against CEOBoard notification, interim leadership, public responseGovernance, communications, legal
Natural disasterEarthquake damages primary office and data centerEmployee safety, facility assessment, operations relocationBCP, employee care, DR activation
Product safety issueReports of product causing customer harmProduct recall decision, liability assessment, regulatory notificationProduct, legal, communications, operations

Step 3: Define Roles and Responsibilities

RolePersonResponsibilities During Exercise
Exercise Director[Name]Overall exercise management; controls timing; introduces injects
Facilitator[Name]Guides discussion; keeps participants on track; manages time
Evaluator(s)[Name(s)]Observes and scores responses against evaluation criteria; takes notes
Crisis Commander[Participant]Leads the crisis response (being tested)
Communications Lead[Participant]Drafts statements and manages stakeholder communications (being tested)
Technical Lead[Participant]Assesses technical impact and directs technical response (being tested)
Legal Advisor[Participant]Advises on legal obligations and liabilities (being tested)
Scribe[Name]Documents decisions, timeline, and action items in real time

Step 4: Build Evaluation Criteria

CompetencyEvaluation CriteriaScore (1-5)Evidence
Detection and escalationWas the incident identified promptly? Was escalation appropriate?
Situation assessmentWas the scope and severity accurately assessed?
Decision-makingWere decisions made with appropriate speed and information?
Communication — internalWere the right people informed at the right time?
Communication — externalWere customer/media/regulator communications appropriate?
CoordinationDid teams work together effectively? Were handoffs smooth?
Plan adherenceWere existing plans followed? If deviated, was it justified?
Resource managementWere people and resources allocated effectively?
Legal and regulatoryWere legal obligations identified and met?
Recovery transitionWas the shift from crisis to recovery well-managed?

Scoring guide:

ScoreDescription
1Not addressed — competency was missed entirely
2Partially addressed — significant gaps or delays
3Adequately addressed — met minimum expectations with some issues
4Well addressed — effective response with minor improvements possible
5Exemplary — exceeded expectations; could serve as a model

Step 5: Execute the Exercise

Facilitation Guide

PhaseFacilitator Actions
Pre-brief (15 min)Welcome; state objectives; explain rules (safe space, no blame); distribute scenario setup
Phase 1: Setup (20 min)Read scenario trigger; ask "What do you do first?"; let team self-organize
Phase 2: Escalation (30 min)Introduce injects at planned intervals; increase pressure; observe decision-making
Phase 3: Peak (30 min)Multiple simultaneous injects; conflicting information; ask for prioritization decisions
Phase 4: Resolution (20 min)Signal situation stabilizing; ask for recovery transition plan; final communications
Hot debrief (30 min)What went well? What surprised you? What would you do differently?

Ground Rules

  • This is a learning exercise, not a test — no blame for mistakes
  • Stay in role — respond as you would in a real crisis
  • Phones on silent (unless part of the exercise)
  • All decisions and communications are "simulated" — nothing goes external
  • If you do not know the answer, that is a finding — say so
  • Evaluators observe silently during the exercise; feedback comes in the debrief

Step 6: Capture Lessons Learned

Output Format

## Crisis Simulation Report: [Scenario Name] — [Date]

### Exercise Overview
- **Scenario**: [Brief description]
- **Type**: [Tabletop / Functional / Full simulation]
- **Duration**: [Actual duration]
- **Participants**: [N] ([List of roles])
- **Facilitator**: [Name]
- **Evaluator**: [Name]

### Scenario Summary
[Description of scenario as it unfolded, including all injects and timing]

### Timeline of Decisions
| Time | Inject / Event | Decision Made | By Whom | Assessment |
|------|---------------|--------------|---------|-----------|

### Evaluation Scorecard
| Competency | Score (1-5) | Strengths | Gaps |
|------------|:-----------:|-----------|------|

### Key Findings
#### What Worked Well
1. [Finding with specific evidence]
2. [Finding with specific evidence]

#### Areas for Improvement
1. [Finding with specific evidence and recommendation]
2. [Finding with specific evidence and recommendation]

### Action Items
| # | Action | Finding | Owner | Priority | Deadline |
|---|--------|---------|-------|----------|----------|

### Plan Updates Required
| Plan | Section | Update Needed | Owner |
|------|---------|--------------|-------|

### Participant Feedback
[Summary of participant self-assessment and suggestions]

### Next Exercise
- **Recommended scenario**: [Based on gaps found]
- **Recommended timing**: [Date]
- **Focus area**: [Specific competency to improve]

Quality Checklist

  • Scenario is realistic and relevant to the organization's actual risk profile
  • Exercise has clear, measurable objectives — not just "practice crisis response"
  • Scenario escalates in complexity and requires real decisions, not just information-sharing
  • Evaluation criteria are defined before the exercise, not invented afterward
  • All key crisis roles are represented as participants
  • Lessons learned are translated into specific action items with owners and deadlines
  • Action items are tracked to completion — not forgotten after the exercise ends

Edge Cases

  • Participants who have never been in a real crisis: Provide more coaching and pre-reading; pair with experienced members; keep the first exercise simple
  • Senior executives who resist participation: Frame it as strategic decision practice, not compliance; keep their time commitment short (2 hours max); make it relevant to their decisions
  • Exercise reveals a critical gap: If the gap is severe (e.g., no backup for a critical system), escalate immediately rather than waiting for the post-exercise report
  • Participants break character or treat it as a joke: Facilitator resets expectations; emphasize real-world consequences; use actual past incidents as context
  • Remote or hybrid exercise: Use video conferencing with dedicated channels for injects; simulate communication challenges by introducing "connectivity issues" for realism
  • Regulatory-mandated exercises: Ensure documentation meets regulatory requirements; involve compliance in exercise design and review
保存したスキル