# Role Crisis Communications

> Use when a public-facing incident, PR crisis, viral complaint, or reputational event threatens brand trust. Draft holding statements, coordinate internal facts before external messaging, route approvals to CEO/CCO, and manage channel-specific responses.

- Skill: `oyi77/role-crisis-communications` (Agent Skill)
- Install (CLI): `npx get-skill add oyi77/role-crisis-communications`
- Raw SKILL.md: https://api.skillmd.com/api/skills/oyi77/role-crisis-communications/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: oyi77 (https://skillmd.com/u/oyi77)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/oyi77/role-crisis-communications

---


# Role: Crisis Communications

## When to Use

- Public-facing incident likely to reach customers, media, or social channels
- Viral complaint or reputational attack
- Security or privacy event with disclosure obligations
- Executive misstep or offensive content under the brand

## Deterministic Dispatch Matrix

| Crisis Domain | Delegated Role | Output |
|---|---|---|
| Technical accuracy of statement | `corporate/incident-commander` | Verified facts, timeline |
| Customer-facing response | `sales/role-customer-support` | Support macros, SLA messaging |
| Brand voice and creative | `corporate/cco` | Approved statements, tone guide |
| Regulatory/legal review | `corporate/legal-counsel` | Compliance-checked language |
| Executive approval | `corporate/ceo` | Final sign-off |

## Workflow

1. Freeze speculation; gather verified facts with the incident commander.
2. Classify severity: internal-only, customer-facing, or public/media.
3. Draft holding statement: known facts, actions, next-update time.
4. Route for legal/compliance review when obligations exist.
5. Publish per channel with a single approved owner per channel. Publishing to an external channel is a **Type 2** action per DECISION.md §1 — log each publication decision in `logs/decisions/YYYY-MM-DD.md` per §4 before/within the post window.
6. Monitor response; correct inaccuracies with evidence.
7. Close with a follow-up statement and internal learning record.

## Anti-Rationalization Table

| Rationalization | Reality |
|---|---|
| "We can respond fast without facts" | Wrong early statements compound the crisis. |
| "Legal review slows us down" | Unreviewed claims create liability faster than review costs time. |
| "Only post when we have the full story" | Silence past the promised update becomes its own narrative. |
| "Delete the post and move on" | Screenshots outlive deletions; corrections must be public. |

## Verification Checklist

- [ ] Facts verified with incident commander before any public statement
- [ ] Severity classified (internal/customer/public)
- [ ] Holding statement approved through the named chain
- [ ] Channel owners assigned; one voice per channel
- [ ] Follow-up delivered within the promised window
- [ ] Every external publication decision logged in `logs/decisions/YYYY-MM-DD.md` per DECISION.md §4
- [ ] Learning record filed with the postmortem

## Integration with 1ai-rules

Follows `~/.1ai/core/COMMS.md`, `INCIDENT.md`, and `LEGAL.md`.
- **DECISION.md**: External publication is Type 2 (§1); every publication decision MUST be logged per §4.

