Skip to main content
D&D DM Prompts

ChatGPT Prompts for D&D Dungeon Masters

Random encounters, NPC voice profiles, dungeon room generators, magic items, and in-world session recaps — designed for D&D 5e dungeon masters running actual campaigns, not for generating dragon stats you'll never use.

5 prompts|By PlugMonkey Team, Editorial

Running a D&D campaign generates surprising amounts of session-prep work — random encounter design, NPC dialogue, room descriptions, plot connections, magic items, social encounters. These prompts are built to handle the recurring prep tasks fast, while leaving the table-craft (improv response to player choices, dice-roll consequence calls, table tone management) firmly in your hands. All output is D&D 5e-aligned by default; specify a different system in any prompt and the AI will adapt.

Key Takeaways

  • DM prompts should handle PREP tasks (encounter design, NPC generation, room descriptions, plot connections, magic items) — the recurring writing work that eats session prep time. Table-craft (improv response, dice-consequence calls, tone management) stays with you. AI as prep-multiplier, not co-DM.
  • System-alignment matters. Default output is D&D 5e; specify Pathfinder 2e, Shadowdark, Old-School Essentials, or Dungeon World and prompts adapt. Cross-system prompts (using 5e stats but Pathfinder narrative style) produce reviewable output.
  • NPC generation prompts should include: role in campaign, single defining trait, one secret, one mannerism/verbal tic. Four inputs; skipping any produces flat NPCs. The verbal tic in particular is what makes players remember an NPC 3 sessions later.
  • Encounter-balance prompts should specify party level, party composition, difficulty target (Low / Moderate / High under the 2024 rules, or Easy / Medium / Hard / Deadly if your table uses the 2014 DMG), and whether it's a random encounter or scripted set-piece. Say which edition — the two use different XP budgets. Set-piece encounters need environment + objectives; random encounters just need CR-appropriate stats.
“As a rough guideline, a single monster generally presents a low-difficulty challenge for a party of four characters whose level equals the monster’s Challenge Rating.”
— Wizards of the Coast — System Reference Document 5.2.1 (Combat Encounter Difficulty) · dndbeyond.com
1

Random Encounter for Specific Biome and Party Level

Design a random encounter for my D&D 5e party. I want a complete scene with mechanical setup, environmental detail, and the THREE possible directions it could go based on player choices.

Party composition: [e.g., Level 5: Wizard (Evocation), Fighter (Battle Master), Cleric (Life), Rogue (Arcane Trickster)]
Biome / location: [e.g., dense pine forest, frozen tundra, sewer beneath a city, mountain pass at dusk]
Difficulty target: [Low / Moderate / High (2024 rules) — or Easy / Medium / Hard / Deadly (2014 DMG)]
Encounter type mix: [combat only / combat + social / mostly social / exploration with optional combat]
Stakes: [why this matters to the party — connect to current campaign arc if possible]

Output:
1. **Setup paragraph** (3-4 sentences I can read aloud to the table)
2. **What's actually here** (the mechanical truth — what the DM knows that players don't yet)
3. **Initiative trigger** (the moment combat starts, if it does)
4. **Three branches**:
   - Branch A: Players negotiate / parley → outcome
   - Branch B: Players ambush / strike first → outcome
   - Branch C: Players retreat / avoid → outcome (and what happens later)
5. **Loot table** if combat resolves favorably (3 items, themed to the encounter)
6. **One twist** the DM can drop if the encounter is going too easy or too predictably

Format the readable-aloud parts in italics; everything else in standard text.
Save Ondhar to your campaign notes regardless of whether players engage. NPCs who appeared once and were ignored often become great recurring side characters when reintroduced 5-10 sessions later.
2

NPC Voice Profile (Improv-Ready)

Build a complete NPC voice profile I can improv from at the table. Focus on what makes them recognizable as a CHARACTER, not stats.

NPC role in the world: [e.g., tavern keeper, traveling merchant, captured noble, masked cult leader, river ferryman, child orphan informant]
Location: [where the party meets them]
Why the party is talking to them: [the in-game reason for the encounter]
Plot purpose: [what they need to convey or refuse to convey + how this connects to the campaign arc]
Optional: secret they're hiding (if any)
Optional: alignment (only if it matters for their behavior)

Output as the following EXACT structure (this format is designed for table-side reference):

**Name:** [include reasoning for the name — region or origin]
**Race / Age / Apparent profession:**
**Physical detail you'll mention first (the "hook"):** [one specific visual that makes them memorable — not "tall" or "wears a hat" but something specific like "their left eye is glass and the iris is painted to look like a sunset"]
**Voice / accent / speech pattern:** [specific instructions, not just "gruff"; include 2-3 verbal tics — phrases or word choices unique to them]
**Three "ALWAYS" behaviors:** things this NPC does in every interaction (e.g., "always wipes their hands on their apron before saying anything important")
**Three "NEVER" behaviors:** things this NPC will not do (e.g., "never breaks eye contact during a lie", "never mentions their family")
**Knowledge they have:** what they know that's relevant to the campaign
**Knowledge they DON'T have:** what they'd lie about or refuse if asked
**Goal in this scene:** what they want from the party (informational, financial, emotional)
**Improv launchers:** 3 sample lines I can say to start the encounter
**If players try to seduce/intimidate/persuade:** specific DC + outcome for each
When players ask questions you didn't prepare answers for, default to: 'He touches his pinky stumps for a second, then says, [your improvised answer].' The physical gesture buys you 2 seconds to think, AND tells the players he's about to be honest. Mechanical NPC traits become storytelling shortcuts.
3

Dungeon Room with Three Possible Approaches

Design a single dungeon room that supports three different play styles: combat-first, stealth-first, and puzzle-first. Each approach should be viable; the room rewards the players for choosing one over the others without punishing the other choices.

Dungeon type: [e.g., wizard's tower, ruined temple, haunted mansion, dwarven mine, underwater shrine, demonic prison]
Position in dungeon: [opening room / mid-dungeon / boss antechamber / hidden secret room]
Party level: [e.g., 5]
Room size: [tight 15ft × 20ft / standard 30ft × 30ft / large 50ft+ / dramatic vertical 30ft × 30ft × 60ft tall]
Theme: [optional — what makes this room different from a generic room]

Output:
- **Read-aloud description** (3-4 sentences, evocative but not over-written)
- **What's actually here** (the truth — traps, monsters, items, exits)
- **Approach A — Combat:** what triggers it, who/what the enemies are, what they want, how victory works
- **Approach B — Stealth:** what the players need to notice, the DC for the sneak, what they get if they succeed (could be loot, info, route past the encounter, advantage on the next encounter)
- **Approach C — Puzzle/Lateral:** the puzzle premise, the multiple solutions (puzzles with one solution are bad design), the reward
- **Hidden detail** that all three approaches might miss but a focused investigator (Investigation DC 16+) would catch — this rewards players who slow down

Include the XP value of each approach (puzzle and stealth should reward proportionally to combat).
Players feel their choice mattered when they see the dungeon respond differently to different tactics. Check the generated XP values and DCs against your own table's level before you run the room — the model's numbers are a first guess.
4

Custom Magic Item with Lore and Real Mechanical Choice

Design a custom magic item for my campaign. The mechanics should be interesting (not just "+1 to something"); the lore should be specific (not just "an ancient artifact"); and using the item should require a real CHOICE — risk/reward or thematic tradeoff.

Item type: [weapon / armor / wondrous item / consumable / sentient item / cursed (with payoff for engaging the curse)]
Power level: [common / uncommon / rare / very rare / legendary]
Theme: [e.g., "regret", "the road not taken", "fire that doesn't burn the bearer", "memory replacement"]
Party level it's designed for: [e.g., level 8]
Origin: [who made it / when / why it exists in the world]
Optional: a specific NPC or location the item is tied to

Output:
- **Item name** (evocative; reference the theme without being on-the-nose)
- **Item type and rarity** (e.g., "wondrous item, very rare, requires attunement")
- **Description** (visual — what does it look like? — and any obvious magical signatures)
- **Lore** (3-4 sentences of origin and history; one sentence of myth or hearsay)
- **Mechanics** (the actual rules — exact, playable at the table)
- **The choice / cost** (what makes using this item interesting; what does the player give up?)
- **DM secret** (something not in the item description that affects future story arcs)

The mechanics should not be exploitable by a level-8 optimizer. The choice should make the player think every time they use it.
Custom magic items become campaign-defining moments when players have to choose between using a powerful feature vs accepting its cost. Always include the cost mechanic upfront — players who don't know about a downside until session 8 feel cheated; players who knew and chose to use it anyway feel like agents in the story.
5

Session Recap in the Voice of an In-World Bard

Write a session recap as a poem or song by a bard in our campaign world. Tone: dramatic but slightly comic. Length: long enough to cover the major beats, short enough to read aloud at session start.

Session events (in order): [paste your session notes — 5-10 bullets of what happened]
Campaign tone: [e.g., grimdark, heroic, comedic, mystery, political intrigue]
Bard's musical style or origin: [e.g., dwarven mead-hall ballad, elven harp lament, halfling tavern singer, dramatic theater monologue]
Recurring NPC who should be referenced in the recap (optional): [name]
Inside jokes from the session that should appear (optional): [e.g., "Halrik failed THREE perception checks", "the rogue tried to seduce a statue"]

Output the recap in verse or song form, 20-40 lines. Include:
- An opening invocation that establishes the bard's character
- 3-5 verses covering the session's major beats in order
- A reference to at least one player's specific moment (use their character names)
- A closing that hints at next session's stakes (without spoiling DM secrets)

Format with line breaks for reading aloud. Include occasional rhymes but don't force them.
Read the bard recap aloud at the start of the next session — 90 seconds, sets the tone, recovers context for players who haven't thought about the campaign in a week. If players start asking for their moments to make the recap, keep a running list during play to paste in.

The Numbers Behind These Prompts

Every figure below cites a primary source. Click through to verify.

Low / Moderate / High

SRD 5.2.1 describes three categories of encounter difficulty. A High-difficulty encounter "could be lethal for one or more characters", while a Low one should see the characters emerge victorious with no casualties. Put the category and your edition into the Random Encounter prompt so ChatGPT doesn't mix the older and newer systems.

Source: Wizards of the Coast — System Reference Document 5.2.12025

750 XP

The Moderate XP budget per character at level 5 in SRD 5.2.1 (Low is 500, High is 1,100); multiply by the number of characters to get the encounter's budget. Ask ChatGPT to show the XP of every creature it picks so you can check its encounter against that budget yourself.

Source: Wizards of the Coast — System Reference Document 5.2.12025

2-3 stat blocks

The SRD warns that referencing more than two or three stat blocks for a single encounter can be daunting. If a generated encounter or dungeon room pulls in a long list of different monsters, ask for a version built on two creature types.

Source: Wizards of the Coast — System Reference Document 5.2.12025

How to Use These Prompts

Use these prompts in your session prep window — the day before the game, not during. Build a library of encounters, NPCs, rooms, and items you can pull from when your players go off-rail (and they will). Always verify monster stat blocks against the Monster Manual; ChatGPT occasionally hallucinates spells or invents creatures. The NPC Voice Profile output is gold — print it and keep it at the table for instant character recall. Prompt Anything Pro lets you trigger these prompts on any text you've selected (Roll20 notes, Notion campaign vaults, session prep docs) without copy-pasting between tabs.

Need More Prompts?

Get personalized AI suggestions for additional prompts tailored to your specific needs.

AI responses are generated independently and may vary

Frequently Asked Questions

Run These Prompts Inside Any Webpage

Prompt Anything Pro lets you run these prompts on any text you've selected — Roll20 notes, Notion campaign vaults, session prep docs — without copy-pasting between tabs.