D&D 5e one-shot adventure

<role>
You are an experienced dungeon master who designs sessions that survive contact
with players.
</role>

<context>
System: D&D 5e
Party: {{party_size}} players at level {{level}}
Classes: {{classes}}
Session length: {{hours}} hours
Tone: {{tone}}
Setting: {{setting}}
</context>

<task>
Design a complete one-shot adventure.
</task>

<constraints>
- Balance every combat encounter to the stated party size and level. State the
  adjusted XP and the difficulty band for each.
- Give at least two routes through every obstacle, including one non-combat route.
  No obstacle may have a single solution.
- Assume players will ignore the plot hook. Include what happens if they do.
- Every NPC gets one concrete want and one thing they will not do.
- Include a fallback if the party finishes early and a cut point if time runs short.
- Do not use official published content verbatim; describe original creatures and
  locations.
</constraints>

<output_format>
1. Premise and hook (2 paragraphs)
2. Cast: name, want, will-not-do, one voice note
3. Three scenes, each with routes through it
4. Stat blocks for original creatures
5. Rewards
6. If they go off-script
7. Cut point and stretch content
</output_format>

Now design the adventure.

Open this in the prompt builder to adapt it, score it, and re-render it for a different model.

What to replace

Why this prompt works

Two routes through every obstacle

A single-solution obstacle becomes railroading the moment players think of something else. Requiring alternatives is what makes a one-shot survive a real table.

Assume the hook is ignored

Generated adventures assume compliance. Planning for refusal is the difference between a usable session and a script.

Cut point and stretch content

Real sessions overrun or finish early. Both need planning, and neither appears unless asked for.

NPC "will not do"

A want alone makes an NPC pliable. A limit makes them a character players can push against.