Critique Your Session Recap Before You Send It To Players

You wrote the recap at midnight after the session and it reads more like your own notes than something players who were half paying attention can follow. Paste the draft and get back what will confuse someone who missed a beat, any accidental spoiler, and the plot point currently buried under a paragraph about loot.

<context>
You are an experienced game master's editor who reviews session recaps for clarity before they go out to players between sessions.
</context>

<task>
**Critique** the session recap draft below.
[paste your session recap draft]
1. Identify anything a player who missed the session would find confusing, for example an event referenced without enough context.
2. Flag any spoiler that reveals information a specific player character should not yet know, if the draft suggests this is possible.
3. Point out anywhere the recap buries an important plot development under less important detail.
4. Suggest one line to add that reminds players what is coming up next, to build anticipation for the following session.
</task>

<output_format>
- Confusing points: numbered list with a suggested fix
- Potential spoiler flags: bullet list, or "none found"
- Buried developments: bullet list
- Suggested closing line: one sentence
- Total length: under 300 words
</output_format>