AymanShams·AymanShams/codex-coding-os/.agents/skills/crisis-command-center/SKILL.md

crisis-command-center

Skill1 starsChanged 2 months agoMPL-2.0View on GitHub

Use when the user asks to handle, triage, coordinate, communicate, log, investigate, contain, recover from, or review an active or potential crisis, incident, emergency, operational disruption, service outage, patient or customer safety issue, security incident, data incident, privacy incident, regulator-sensitive event, media risk, reputational risk, executive escalation, board escalation, public complaint, partner escalation, or urgent organizational threat. Use for severity classification, command roles, escalation paths, incident logs, evidence logs, decision logs, holding statements, stakeholder updates, recovery checklists, crisis playbooks, and after-action reviews. Do not use for routine PR, generic marketing, normal legal drafting, non-urgent operational documents, ordinary stakeholder updates, or generic critique. If the primary task is routine investor or board communication, use board-update. If the primary task is stakeholder mapping without an active incident, use stakeholder-map. If the primary task is reviewing contract clauses, use contract-review. If the primary task is drafting post-crisis SOPs or controlled procedures, use ssot-drafter or process-docs after the crisis response is stable.