Skip to content

hoavdc/CodexKit / skills/codexkit-crisis-communication

codexkit-crisis-communication

Unverified

Draft crisis communication packages including holding statements, stakeholder updates, Q&A documents, and internal briefs. Follows ICS (Incident Command System) communication principles. Use during PR crises, data breaches, product recalls, or any event requiring rapid coordinated messaging.

Crisis Communication

When to Use

  • During a PR crisis, data breach, or security incident
  • When a product issue affects customers at scale
  • When media attention or social media escalation requires response
  • When a compliance violation or legal issue needs external communication

Procedure

Step 1 — Severity Assessment

LevelCriteriaResponse TimeApproval
CriticalPublic safety, data breach, regulatory< 1 hourCEO + Legal
HighMajor service disruption, media coverage< 4 hoursVP + Comms
MediumNotable customer impact, social media trending< 24 hoursDirector + Comms
LowMinor issue, limited audience< 48 hoursComms team

Step 2 — Fact Gathering

Before writing anything, document what is known:

CategoryDetails
What happened?[Factual description — no speculation]
When?[Timeline of events]
Who is affected?[Customers, employees, partners — numbers]
What caused it?[Known root cause, or "under investigation"]
What actions taken?[Steps already taken to address]
What's next?[Planned actions and timeline]

Rule: Only communicate confirmed facts. Never speculate.

Step 3 — Holding Statement

Draft the initial public response (use within first hour):

[Company] is aware of [brief description of incident].
We are actively investigating and have taken immediate steps to [action taken].
[Affected parties] may experience [specific impact].
We will provide an update by [specific time].
For questions, contact [channel].

Principles:

  • Acknowledge the situation
  • Show empathy for those affected
  • State what you're doing about it
  • Commit to a specific update time
  • Provide a contact channel

Step 4 — Q&A Document

Prepare answers for anticipated questions:

QuestionAnswerApproved by
How many users are affected?[Specific number or range]Legal
Is my data safe?[Honest, specific answer]Security + Legal
What should I do?[Clear action steps]Product
Will this happen again?[Prevention measures]Engineering
Will you compensate affected users?[Policy decision]Executive

Step 5 — Stakeholder-Specific Messages

AudienceChannelToneKey Message
CustomersEmail, in-appEmpathetic, transparentImpact + what we're doing + what you should do
EmployeesAll-hands, SlackHonest, calmWhat happened + talking points + don't speculate publicly
MediaPress releaseProfessional, factualStatement + background + contact
RegulatorsFormal letterCompliant, detailedFull disclosure per requirements
Board / investorsDirect callStrategicImpact assessment + response + outlook

Step 6 — Update Cadence

PhaseFrequencyChannel
First 24 hoursEvery 2–4 hoursStatus page, social media
Day 2–3Every 8–12 hoursEmail, blog
Day 4–7DailyBlog, status page
Post-resolutionFinal update + postmortemBlog, email

Inputs

InputRequiredFormat
Incident descriptionYesWhat happened
Affected partiesYesWho and how many
Known factsYesConfirmed information only
Actions takenYesWhat has been done so far
Legal review statusRecommendedHas legal approved messaging?

Output

## Crisis Communication Package — [Incident Name]

### Severity: High | Status: Active
**Incident Lead:** [Name] | **Comms Lead:** [Name]

### Holding Statement
[Ready-to-publish statement]

### Q&A
[Prepared answers for 10–15 anticipated questions]

### Stakeholder Messages
[Customized message per audience]

### Update Schedule
[When and where next updates will be published]

Definition of Done

  • Severity assessed and response timeline set
  • Facts separated from speculation
  • Holding statement drafted within response window
  • Q&A covers top 10 anticipated questions
  • Messages tailored per stakeholder group
  • Update cadence committed and communicated

Quality Criteria

  • All placeholder sections are filled with domain-specific content
  • Structure follows the relevant industry standard or framework
  • Language matches target audience (technical / executive / legal)
  • Output is ready for review — not a rough draft requiring major rework

Verification (4C)

CheckQuestion
CorrectnessDoes the draft structure follow the stated framework or industry standard?
CompletenessAre all required sections present with substantive (not placeholder) content?
Context-fitDoes tone, detail level, and terminology match the intended audience?
ConsequenceIf sent to the intended recipient without further editing, what would fail?

Edge Cases

  • No existing template for this type — Use the closest available template and document all customizations made.
  • Stakeholder requirements conflict — Flag conflicts explicitly in the draft. Do not silently choose one requirement over another.
  • Output required in multiple formats — Produce the canonical format first, then derive others. Note any formatting limitations.

Changelog

  • v1.0.0 — Initial release
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 464kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 318kUpdated Claude CodeCodexUnverifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 318kUpdated Claude CodeCodexUnverifiedInstall