Claude prompt for storytelling: Origin Story (Workflow)
Claude · Storytelling · Workflow
You are a systems thinker using Claude for storytelling, specifically origin story.
Job: why this exists.
Audience: founders. Constraint: scene not resume.
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 founders need origin story with the rule: scene not resume. Most failed runs trace back to missing audience or success criteria — this prompt adds both. 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 origin story brief separates the job so you can iterate once, not ten times. Swap only nouns when adapting — keep the process intact.
Why this prompt works
- Repeats the hard constraint: scene not resume.
- Forces an output contract: headings, examples, and a final version.
- Names a clear job so Claude does not wander into generic advice.
- Asks for a self-check pass, which cuts hallucinated details.
- Locks the audience (founders) before style so tone stays honest.
How to use it in Claude
Arcs, case stories, and audience journeys. Keep that context in the thread when you iterate. If the first answer is vague, reply with the constraint again: scene not resume. This Workflow path is for founders who care about why this exists. Name the success metric aloud: why this exists. If the draft cannot pass it, do not polish prose yet. Save the winning variant for origin story — teams with a short library ship faster.
Start with the ugly first pass for origin story. Name what is wrong in five bullets, then rerun in Claude. For origin story in storytelling, the failure mode is usually missing constraint. This prompt blocks that by design — especially "scene not resume". Expect two minutes customizing and two minutes editing for Workflow output. Anthropic models still need your facts for origin story; they cannot invent metrics or brand rules. brand and narrative teams teams bookmark slug origin-story-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 (founders, offer, timeline).
- Confirm the constraint is still visible: scene not resume.
- 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 Origin Story, 3 short sections, bullet list of recommendations, closing line that states scene not resume. Facts you supply appear; nothing invented.
Common mistakes
- Asking for origin story plus three other jobs in one message.
- Using the Workflow prompt but editing it into a vague one-liner.
- Deleting "scene not resume" to save space — that is usually the whole point.
Expert notes
Anthropic users working on origin story in storytelling should treat "scene not resume" as non-negotiable. Arcs, case stories, and audience journeys. When founders run the Workflow variant, they usually care about step order, checkpoints, and handoffs more than length.
If text output feels generic, re-paste scene not resume 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 origin story 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
- Compare against other Claude angles on the same use case before you standardize.
- The Workflow variant is for step order, checkpoints, and handoffs.
- founders should recognize themselves in the first paragraph.
- State the job (why this exists) in one line before any style talk.
- If text output drifts, re-anchor with scene not resume.
FAQ
- What is a Claude prompt for origin story?
- It is a structured brief that tells Claude how to produce storytelling output for founders. This workflow version stresses step order, checkpoints, and handoffs and keeps "scene not resume" 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 "scene not resume" should stay unless your brief truly changed.
- Why use the workflow angle for origin story?
- Different angles solve different failures. Workflow helps when founders 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.