Dry, lifeless AI summaries aren’t an AI problem. They’re a prompt problem. One Reddit user figured out how to make the AI tell a story instead of filing a report.
The original poster in r/ChatGPTPromptGenius was tired of summaries that were technically accurate but completely forgettable. So the author spent time experimenting with prompt structures until landing on something that actually works. The approach: give the AI a specific role, a clear narrative goal, and tight style constraints. The result is output that reads like documentary narration instead of a Wikipedia stub. The difference between a forgettable bullet-point recap and something you’d actually want to read comes down to about three extra lines of prompt setup.
Why This Works
The author breaks down three key insights from the experiment:
- Context changes everything. Saying “summarize this” gives the AI no direction on how to frame information. Assigning a role like “master storyteller and historian” completely shifts the output. The AI stops organizing facts and starts building a narrative arc around them.
- Combined roles beat single roles. “Writer” is too vague. “Master storyteller skilled at weaving factual information into engaging narratives” is a specific persona with a specific skill set. The more specific the role description, the less the AI defaults to its generic summary mode.
- XML structure helps you think. Even though the AI doesn’t process XML like code, organizing a prompt into labeled sections forces you to be precise. No more dumping a messy block of vague instructions. You end up defining the role, the goal, the tone, and the format separately, which means each piece gets actual thought instead of being buried in a wall of text.
What stands out here is that the structure does double duty. It makes intent clearer to the AI, and it forces you to actually think through what you want before you ask for it. Most people skip that second part entirely.
🎯 Use Cases
- Summarizing long research papers or reports into something a colleague would actually read instead of skim
- Turning dense technical documentation into onboarding material that new hires can follow without a guide
- Converting meeting notes or call transcripts into narrative recaps that capture decisions, not just talking points
- Making historical content or case studies more engaging for audiences who need context, not just facts
Prompt of the Day
Here’s the full template from the original post. Drop your content into [CONTENT_TO_SUMMARIZE]:
<Prompt>
<Role>You are a master storyteller and historian, skilled at weaving factual information into engaging narratives. Your goal is to summarize the provided content not as a dry report, but as a compelling story that highlights the key events, characters, and transformations described.
</Role>
<Context>
<Instruction>Read the following content carefully. Identify the core subject, the primary actors or elements involved, the sequence of events or developments, and the ultimate outcome or significance. </Instruction>
<NarrativeGoal>
Your summary must read like a narrative. Employ descriptive language, establish a sense of progression, and evoke the essence of the information. Avoid bullet points and simple factual recitations. Focus on creating a cohesive and interesting story from the facts.
</NarrativeGoal>
<Tone>Engaging, informative, and slightly dramatic (where appropriate to the source material), but always factually accurate.</Tone>
<OutputFormat>A single, flowing narrative paragraph or a series of short, interconnected narrative paragraphs.</OutputFormat>
</Context>
<Constraints>
<Length>Summarize concisely, capturing the essence without unnecessary detail. Aim for 150-250 words, adjusting based on content complexity.</Length>
<Factuality>Strictly adhere to the information presented in the source content. Do not introduce outside information or speculation.</Factuality>
<Style>Use active voice, strong verbs, and evocative adjectives. Think about how a documentary narrator would present this information.</Style>
</Constraints>
<Content>
[CONTENT_TO_SUMMARIZE]
</Content>
</Prompt>A few things worth noting about the structure. The 150-250 word length constraint is a smart guardrail. Without it, “narrative mode” can spiral into something way too long, especially on dense source material. The factuality constraint keeps the storytelling from going creative in ways you don’t want. A good narrator sticks to what happened; they just make it compelling. And “think about how a documentary narrator would present this” is specific enough that the AI actually uses it rather than defaulting to a neutral, flat voice.
Variations Worth Testing
The author suggests experimenting with role combinations. Some adjustments that make sense:
- Swap “historian” for “journalist” if the source material is news-based. The journalist framing pushes the AI toward a sharper lede and a tighter structure.
- Add a target audience inside the Role section (“…for an audience of non-technical executives”). This one adjustment often eliminates jargon without you having to list every term to avoid.
- Change the OutputFormat to “three short paragraphs with a clear beginning, middle, and end” when you need the output to fit a specific layout like a newsletter or a slide deck.
- Tighten the length constraint to 100 words for quick briefings where every word has to earn its place.
The core principle applies across all of them: the more precisely you define the role and the output goal, the less the AI has to guess about what you actually want. And when it stops guessing, the output stops being generic.
The original discussion is in r/ChatGPTPromptGenius if you want to see the full thread and share what variations you come up with.
Try my ‘vivid narrative’ prompt
by u/Distinct_Track_5495 in ChatGPTPromptGenius