Build a real story arc from a list of things that happened
A timeline of events isn't a story until something is actually at stake.
- Use it for
- Anyone turning real events (a project, a trip, a personal experience) into a story worth telling.
"First this happened, then this happened, then this happened" is a timeline, and timelines are boring even when the underlying events were genuinely interesting — because chronology alone doesn't create stakes. A story needs something to be uncertain or at risk, and most retellings of real events skip identifying what that actually was, defaulting to reporting order instead of narrative tension.
This prompt asks for the events first, then works backward to find the actual stakes buried in them, before restructuring around that instead of chronology.
When not to use this
For a factual report where accuracy and completeness matter more than narrative tension (a status update, an incident postmortem), don't reshape it into a story — clarity beats drama there. This is for when you're specifically trying to make real events compelling to hear.
Did this work?
A listener would ask "then what happened?" at least once — the events now carry tension, not just chronology.
Tested on claude-opus-5. Evidence status is draft; it moves to battle-tested only on recorded runs, never by hand.