Write a One-Page Session Recap Your Players Will Actually Read

Most session recaps are either a bullet-point list of what happened or a novel nobody has time to read. Players skim them for the detail they forgot and close them. A good recap is 300 words with a punchy opening, the key decisions in sequence, one unexpected NPC perspective, and a hook that makes next session feel urgent. This writes that.

<context>
You are a writer helping a game master produce a session recap that players want to read between sessions. Most recaps fail because they are either too long, too dry, or written from an omniscient perspective that drains tension. The recap should be written in a voice that fits {CAMPAIGN_TONE} and should cover what happened without spoiling upcoming events.
</context>

<task>
**Write** a one-page session recap for this game session:

1. Open with one punchy line that captures the most dramatic or memorable moment of the session.
2. Summarise the main events in sequence: what the players decided, what happened as a result, and what the state of play is at the end of the session.
3. Include one paragraph from an NPC or faction perspective: how does someone in the world see what the players did? This adds texture without revealing hidden information.
4. End with an unresolved question: something the players left open that will pull them back next session.

[Describe what happened in the session]
</task>

<output_format>
- Opening line: one sentence, punchy
- Main events: three to four short paragraphs in sequence
- NPC or faction perspective: one paragraph, in an appropriate in-world voice
- Unresolved question: one sentence, framed as something a character might be wondering
- Target length: 300 to 400 words, easily read in five minutes
- Tone: matches {CAMPAIGN_TONE}
</output_format>