ChatGPT Prompts for Dungeon Masters: NPCs, Hooks and Recaps

Give me three plot hooks that pull [PARTY LEVEL] characters into [LOCATION] in my original setting. For each hook, write one sentence on the stakes and one on the first clue. Then pick the hook that fits my notes in [CAMPAIGN NOTES] best and give one reason. Make up the hooks and first clues yourself, then tell me what I must confirm from my notes. Do not invent facts about my world beyond [CAMPAIGN NOTES]; tag those gaps [VERIFY]. Output three bullets, then a final line naming the pick.

Build a quest chain in five numbered steps for a party that wants [PARTY GOAL]. Each of the first four steps needs a location, an obstacle and the reward that moves them to the next step. Step five needs a location, an obstacle and the payoff. Set it only in [SETTING NAME], a world I made myself, and keep it clear of any published adventure. Places I have: [PLACE LIST]. Use only these places; invent only the obstacles and rewards. If [PLACE LIST] has fewer than five places, reuse a place and say so. If a place from my list is too vague to use, write [VERIFY] on that step rather than adding a new one. Keep each step under 40 words.

Here is a rumour I want to seed in [TOWN NAME]: [ONE LINE RUMOUR]. The truth behind it is: [TRUTH]. Using only [TOWN NOTES], write two options each for Who spreads it, First clue and When players hear it. Mark one option per field as your pick and give a one line reason for each pick. If a place or name is missing from my notes, write [VERIFY] there rather than inventing it. Output the three fields with both options and the pick marked, and stay under 160 words.

Rewrite my side quest below for a player who skipped the last session: [PASTE SIDE QUEST]. Keep it to 90 words, put the reward in the first sentence and name the one NPC who gives the quest. Use only facts from my paste and do not invent names, places or deadlines. If my paste names no reward, write [VERIFY] as the first sentence's reward. If my paste names no quest giver, write [VERIFY] rather than inventing an NPC. Output a short recap paragraph, then one line saying what to do first.

Plan a six week story arc for [PARTY NAME] at [SESSIONS PER WEEK] sessions per week, building toward [CLIMAX]. Give one row per week: the scene, the choice the players face and the consequence I will track. Draft the scenes, choices and consequences as proposals I can keep or drop. Do not invent past events beyond [CAMPAIGN NOTES]; tag references to them [VERIFY]. Output a six row table with columns Week, Scene, Choice and Consequence.

My encounter felt [TOO EASY OR TOO DEADLY] at [PARTY LEVEL] with [NUMBER OF PLAYERS] players. Encounter setup: [ENCOUNTER SETUP]. Here is what happened: [SESSION SYMPTOMS]. List the three most likely causes in plain words, then one fix for each. If a fix names a creature, give it a name you make up for this table. Mark every rule threshold or stat value you suggest as [VERIFY] against my own rulebook, and do not invent monster stats. Output a numbered list of three causes with their fixes.

Describe the battle site for [ENCOUNTER NAME] in [SETTING NAME]: size: [GRID DIMENSIONS] (for example 30 by 40 squares), light, one hazard, two cover spots and one exit. Keep it to 80 words I can read aloud. The light, hazard and cover spots are new ideas you may propose inside the area [MAP NOTES] describes. Do not invent rooms or landmarks beyond it. If [MAP NOTES] names no exit, write [VERIFY] on Exit. Output a labelled block with the headings Size, Light, Hazard, Cover and Exit.

Suggest three original creatures to replace the [FOE TO REPLACE] in my fight. Setting notes: [SETTING NOTES]. For each, give a one line tactic and a reason it suits [PARTY SIZE] players. Rank the three from best fit to weakest and say why the top one wins in 25 words. Coin each creature at this table; do not invent a stat value, and if [SETTING NOTES] gives no climate or culture cue, write [VERIFY] on that row rather than guessing. Output a ranked list with Rank, Creature, Tactic and Why it fits.

Write a checklist for running an ambush scene for [PARTY NAME] at [LOCATION]. Include 7 items: the trigger, what the foes do in round one, the escape route, the sound cue, the first clue, the retreat rule and the reward for listening. Treat the foes' round-one actions as my table's to accept or cut, and invent the sound cue and first clue yourself. Do not invent extra foes or terrain beyond [SCENE NOTES]. If [SCENE NOTES] gives no escape route, write [VERIFY] there. Output a numbered checklist, no more than 12 words per item.

Compare a stealth encounter and a head on fight for [ENCOUNTER GOAL] with my players, who are [PLAYER TYPES]. Cover how long each takes to run, the chance players feel cheated and the story each one leaves behind. Give your judgment on run time, fairness and story as suggestions. Session notes (player habits at the table, such as scouting or rushing in): [SESSION NOTES]. Use [SESSION NOTES] only for facts about my players and do not invent player preferences; tag each guess [VERIFY]. Output a three row table with columns Factor, Stealth and Open fight, then a two sentence verdict.

Build a loot table with six rows for a [LEVEL BAND] party in [SETTING NAME] using [GAME SYSTEM NAME]. Columns: Item, Story hook, Who wants it, Downside and Value to check. Keep items original and tie each one to [CAMPAIGN NOTES]. Item names, hooks, claimants and downsides are new ideas you may propose; only rules and amounts must stay [VERIFY]. Do not invent magic rules or amounts; write [VERIFY] in that column. Output the table, then one sentence on pacing.

Build a cursed item card for [ITEM NAME], whose power in story terms is [WHAT IT DOES]. Offer three story costs the wielder pays and one rival claimant drawn from [CAMPAIGN NOTES], then pick the cost that creates the most table tension. Keep the power story based, with no mechanics or dice values. Use original item names only, never names from a published book or game. If my notes name no rival, write [VERIFY] rather than inventing a person. Output the completed card in under 120 words.

Read my reward list below for [GAME SYSTEM NAME] and say which items are too strong, too weak or too similar: [PASTE REWARD LIST]. Give a one line verdict for each item, then rewrite the three weakest with a story reason. Give the rewrites names that exist only at this table. Use the party facts in [PARTY NOTES] only and do not invent stats. Flag any balance number as [VERIFY] against my rulebook. Output a three column table: Item, Verdict and Rewrite.

Check my loot handout plan before the session: [PASTE LOOT PLAN]. Tick six checks: each item has a story reason, nobody is left out, the cost is clear, the item can be sold or traded, the clue is visible and the rule source is named for [GAME SYSTEM NAME]. Mark any check you cannot confirm from my plan as [VERIFY]. Do not invent items or rules. Output a checklist with a yes, no or VERIFY mark on each line.

Give three reward options for players who just saved [NPC NAME] from [THREAT]. Each option gets a one sentence reward and a reason it fits [CAMPAIGN NOTES]. Pick the one that moves the story forward most and say why in two lines. Name each reward as something that exists only in this campaign. Do not invent names or places I did not give. If [CAMPAIGN NOTES] name no open thread, write [VERIFY] on the pick reason. Output three numbered options, then a final line naming the pick.

Turn my messy session notes into a 150 word recap for players: [PASTE SESSION NOTES]. Write it in the past tense, name the party as [PARTY NAME] and end with one open question. Use only what I wrote. If I did not say who won the fight, write [VERIFY] rather than inventing the outcome. Output a title line, then the recap.

Ask me exactly 5 questions about [SESSION DATE] before you write anything: the turning point, the NPC who surprised us, what the party lost, the next goal and any clue I missed. Wait for my answers. Then write a 100 word read-aloud cold open for next session in present tense. Do not invent answers I did not give; if I skip a question, write [VERIFY] on that beat.

Turn my notes into a session log table with columns Scene, Who acted, What changed, Open thread and Missing detail. Use [SESSION NOTES] only and list each scene in order. If there are more than 8 scenes, merge the smallest and say which. Do not invent events. Mark any blank as [VERIFY] for me to fill. Output a table with at most 8 rows.

Score my session recap below from 1 to 5 on clarity, pace and the hooks it leaves for next time: [PASTE RECAP]. Then list the two lines that would confuse a player who missed the game and rewrite them. Do not invent events or names that are not in my draft. Flag any gap as [VERIFY]. Output a score line, then two before and after pairs.

Make a prep checklist for my next session of [SESSION LENGTH] on [SESSION DATE]. Include 8 items covering the recap, open threads, NPC voices, maps, handouts, a safety check in, timing that fits [SESSION LENGTH] and the cliffhanger. Build it from [PREP NOTES] only and do not invent prep items the notes contradict. If no map is named in [PREP NOTES], write [VERIFY] on the maps item. Output 8 checkboxes, each under 12 words.

Write a session zero questionnaire with 6 numbered questions for a new table of [NUMBER OF PLAYERS] players at [EXPERIENCE LEVEL]. Cover tone, lines and veils, combat pace, death rules, what to do about a missed session and table etiquette including phones. Keep the wording friendly and plain. Invent no house rules; tag any rule question that needs my rulebook as [VERIFY]. Output a numbered list only.

Draft a homebrew rule card for [RULE NAME]. Trigger: [WHEN IT APPLIES]. Effect in words: [WHAT CHANGES]. Propose the Limit in words, such as once per scene or session, and tag any number you are unsure of [VERIFY]. Draft an Exception (when it does not apply) that fits the trigger and effect. Name the rule in [REPLACED RULE NAME] and list at most 2 lines of conflicts. Keep the card under 120 words. Do not invent numbers or dice values. Output the card, then the Conflicts line.

My table keeps arguing about [RULE TOPIC] in [GAME SYSTEM NAME] during play. Here is what happens: [DESCRIBE THE ARGUMENT]. Give three likely causes in plain words, then one house ruling to try for one session. Do not invent official wording or quote any rulebook. Name the rule topic I should look up in my rulebook, tagged [VERIFY]. Do not give page or rule numbers. Output a numbered list of three causes and a single ruling, under 150 words.

Compare two versions of [RULE NAME] for my table. Version A is [VERSION A IN WORDS] and version B is [VERSION B IN WORDS]. Compare speed of play, fairness to [PLAYER TYPES] and how easy the rule is to explain. Use my notes only and do not invent playtest results. Mark any claim I have not tested as [VERIFY]. Output a three row table with columns Factor, Version A and Version B, then a one line pick.

Rewrite my homebrew rule below for a new player who has never played [GAME SYSTEM NAME]: [PASTE RULE TEXT]. Use short sentences, no more than two game terms, and a one line example. Keep it under 90 words. Do not invent rules my text does not contain. Tag any term you are unsure of as [VERIFY]. Output the rewrite, then the example line.