Skip to main content

write-an-incident-communication-plan

Write an incident communication plan for audiences, triggers, verified facts, uncertainty, channels, approvals, accessibility, cadence, correction, and closeout. Use when service, safety, security, privacy, operational, or public incidents require timely coordinated updates.

Source facts

Repository
protosphinx/sphinxstack
Last source activity
July 29, 2026 at 13:55
Detected SKILL.md language
English
Stars
3
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
2 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
write-an-incident-communication-plan
category
write
description
Write an incident communication plan for audiences, triggers, verified facts, uncertainty, channels, approvals, accessibility, cadence, correction, and closeout. Use when service, safety, security, privacy, operational, or public incidents require timely coordinated updates.
# write-an-incident-communication-plan Communication is part of harm reduction and operational coordination. ## When to use - Use before incidents or during a controlled planning phase. - Do not promise facts, causes, restoration times, safety, or absence of impact without evidence. ## Procedure 1. Define incident classes, audiences, harms, jurisdictions, obligations, authority, and communication objectives. 2. Map affected people, employees, customers, regulators, partners, vendors, media, public, and internal responders. 3. Set triggers, priority, initial-update time, cadence, channel, owner, approver, backup, and translation. 4. Create templates for acknowledgment, impact, protective action, workaround, uncertainty, investigation, recovery, correction, and closeout. 5. Separate operational status, legal or regulatory notice, customer support, and public communication while reconciling facts. 6. Protect privacy, safety, security, whistleblowers, investigations, and privilege. 7. Design accessible, language-aware, low-bandwidth, out-of-band, and channel-failure alternatives. 8. Rehearse conflicting facts, missed deadline, wrong statement, unavailable approver, and cross-region incidents. ## Done - An incident communication plan records audiences, triggers, facts, templates, cadence, channels, roles, approvals, safeguards, and correction - Scenario, deadline, authority, fact, uncertainty, accessibility, translation, channel-failure, correction, and closeout checks verify readiness
View on GitHub