Claude prompt for storytelling: Crisis Narrative (Workflow)
Claude · Storytelling · Workflow
You are a hands-on practitioner using Claude for storytelling, specifically crisis narrative.
Job: what happened next.
Audience: comms. Constraint: facts dated.
Working style: operational. Optimize for step order, checkpoints, and handoffs.
Process:
1. Restate the brief in one sentence and list missing facts as questions.
2. Draft the artifact.
3. Stress-test it against the constraint.
4. Return a final version plus 3 numbered improvements.
Output contract: use headings, short paragraphs, and concrete examples. No filler. No invented statistics.
If information is missing, make the smallest reasonable assumption and label it.Use this Claude storytelling template when comms need crisis narrative with the rule: facts dated. Teams report saving 15–30 minutes per task when prompts include constraints up front. The workflow version uses operational language and targets step order, checkpoints, and handoffs.
When to use this prompt
For Anthropic models, storytelling prompts fail when they mix strategy and execution. This crisis narrative brief separates the job so you can iterate once, not ten times. Pair it with a real sample from your portfolio for best results.
Why this prompt works
- Uses operational language that matches how practitioners actually brief work.
- Forces an output contract: headings, examples, and a final version.
- Separates draft from critique so you can steal the structure later.
- The workflow angle adds step order, checkpoints, and handoffs without extra fluff.
- Repeats the hard constraint: facts dated.
How to use it in Claude
Redact client names; keep structure. Slug crisis-narrative-workflow is your canonical URL for this brief. Save the winning variant for crisis narrative — teams with a short library ship faster. Use operational follow-ups only — mixing tones mid-thread confuses Anthropic models. When comms review output, they should see step order, checkpoints, and handoffs without hunting for it. Name the success metric aloud: what happened next. If the draft cannot pass it, do not polish prose yet.
Run a constrained version and a wild version of crisis narrative. Keep structure from one and energy from the other. For crisis narrative in storytelling, the failure mode is usually missing constraint. This prompt blocks that by design — especially "facts dated". Expect two minutes customizing and two minutes editing for Workflow output. Anthropic models still need your facts for crisis narrative; they cannot invent metrics or brand rules. brand and narrative teams teams bookmark slug crisis-narrative-workflow when step order, checkpoints, and handoffs matters.
Step-by-step
- Open Claude and paste the prompt block unchanged.
- Replace placeholders with your project facts (comms, offer, timeline).
- Confirm the constraint is still visible: facts dated.
- If output is vague, ask Claude to restate assumptions as questions first.
- Reply with one fix list, then regenerate the final version only.
Example output
Example output shape: H1 with Crisis Narrative, 3 short sections, bullet list of recommendations, closing line that states facts dated. Facts you supply appear; nothing invented.
Common mistakes
- Asking for crisis narrative plus three other jobs in one message.
- Using the Workflow prompt but editing it into a vague one-liner.
- Ignoring the output contract headings.
Expert notes
Anthropic users working on crisis narrative in storytelling should treat "facts dated" as non-negotiable. Arcs, case stories, and audience journeys. When comms run the Workflow variant, they usually care about step order, checkpoints, and handoffs more than length.
If text output feels generic, re-paste facts dated as the first follow-up message — do not rewrite the whole prompt.
Comparison / variations
| Approach | When | Tweak |
|---|---|---|
| Bare request | You only need a spark | Write a crisis narrative piece. |
| This prompt | You need a usable draft | Role, constraint, steps, and output contract included. |
| Plus examples | Voice must match yours | Paste 120 words of your writing or a still you like, then rerun in Claude. |
Key takeaways
- Keep facts dated visible in the prompt, not only in your head.
- If text output drifts, re-anchor with facts dated.
- The Workflow variant is for step order, checkpoints, and handoffs.
- State the job (what happened next) in one line before any style talk.
- comms should recognize themselves in the first paragraph.
FAQ
- What is a Claude prompt for crisis narrative?
- It is a structured brief that tells Claude how to produce storytelling output for comms. This workflow version stresses step order, checkpoints, and handoffs and keeps "facts dated" in the instructions.
- How do I customize this Claude storytelling prompt?
- Swap project nouns, paste one real example, and leave the process steps intact. The constraint "facts dated" should stay unless your brief truly changed.
- Why use the workflow angle for crisis narrative?
- Different angles solve different failures. Workflow helps when comms need step order, checkpoints, and handoffs. It is not longer for its own sake — each line has a job.
- Is this Claude prompt updated for 2026?
- Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Anthropic models. Always verify facts before client delivery.