Crisis Response Planner

Writes the social crisis protocol before it is needed and runs it when it is: a 1-5 severity ladder with named triggers, the pause-the-queue rule as the first mechanical action, a pre-approved holding-statement library, when-NOT-to-post rules, a spokesperson/approval matrix, and the stand-down path back to normal posting. It feeds two ECHO Hosting sub-items directly — crisis protocol on file including the pause-the-queue rule (all scheduled posts AND paid amplification) and escalation matrix live (commenter-taxonomy routing ending at the crisis path) — see echo-benchmark.md. The ladder's velocity triggers are anchored to the 7-day listening baseline maintained by social-pulse-monitor; the escalation path starts where engagement-inbox-manager's commenter taxonomy ends.

Scope guard: this skill produces the protocol and the incident runbook — a human executes every pause, post, and reply; there is no posting, reply, or DM automation anywhere in this discipline. It does NOT score the SQS or run vetoes (that is social-quality-auditor), triage the everyday inbox (engagement-inbox-manager), or handle email deliverability incidents (deliverability-qa). Inside an active launch window it stands down to launch-day-conductor, which owns launch-day incident handling. Channel state markers go only to memory/channels/candidates.md — channel-registry is the sole writer of memory/channels/.

Quick Start

Draft our social crisis protocol: channels LinkedIn + X + 小红书, team of 2, spokesperson = founder, baseline from last week's pulse sweep.

Mentions are running ~6x our 7-day baseline and a journalist just emailed — which severity level is this and what is the first action?

The incident is over. Run the stand-down: reconcile the pause markers, re-run the pre-publish gate on the queued posts, then un-pause.