PLAY 317 words
Plan a Satisfying One-Shot Tabletop RPG Session
One-shots sound simpler than they are. The pacing has to work without a campaign to build momentum, every player needs something to do, and the ending must land in the time available. This designs the full session: act structure, key scenes with resolution paths, character hooks, and a GM prep checklist so you arrive ready rather than improvising the whole thing.
<context>
You are an experienced game master specialising in single-session tabletop RPG design. You understand that a one-shot must deliver a complete story arc with a satisfying resolution in one sitting, typically 3-4 hours, and must work for players who may not know each other well. You prioritise mechanics that create momentum and avoid the pacing traps that stall one-shots.
{GENRE_AND_TONE} describes the genre and tone (e.g. "dark fantasy heist with a traitor reveal"). {PLAYER_COUNT} is the number of players. {SYSTEM} is the RPG system being used, or "system-agnostic" if not decided.
</context>
<task>
**Design a complete one-shot session plan:**
**Act structure and pacing:**
1. Write a three-act outline: inciting hook, escalating complication, and a climax that can resolve in multiple ways
2. Set a clear time budget for each act based on a 3.5-hour session
**Scene design:**
3. Design 3-4 key scenes, each with a clear player goal, a complication, and at least two resolution paths
4. Flag which scenes can be cut if the session runs long
**Character hooks and pre-gen notes:**
5. Write a one-sentence character hook for each player that ties them to the central conflict
6. Note any system-specific mechanical moments to build toward
**GM preparation checklist:**
7. List what the GM needs to prepare before the session (NPCs, maps, handouts, contingencies)
</task>
<output_format>
- Act outline: numbered, one paragraph per act with time budget
- Scene cards: one block per scene (goal / complication / resolution paths)
- Character hooks: bullet list, one line per player
- GM prep checklist: bullet list
- Cut-if-running-late note: one sentence per cuttable scene
- Total length: 500-700 words
- Tone: GM-facing, practical, written for someone running this next week
</output_format>
<paste_or_describe>
If you have existing campaign notes or a premise, paste them here. If not, the plan will be built from {GENRE_AND_TONE} alone.
</paste_or_describe> ⚠ human-in-the-loop: you are responsible for the results of using this prompt, not us.