The blank page is the hardest part of running a game. This gives a new or busy DM a runnable start: a hook players will bite on, a session-zero to set tone and boundaries, and a first adventure with enough structure to run confidently — plus the flexibility for when the party inevitably does something you didn't plan.
What This Skill Produces
- The premise & hook — a one-line pitch and a reason the party is here, together
- A session-zero kit — tone, content boundaries/safety tools, and table expectations
- The first-adventure outline — opening scene, 3–5 beats, a branch or two, a satisfying climax
- NPCs & encounters — a few characters with a want and a voice, and encounters scaled to party level and size
- Improv fallbacks — what to do when players skip the plot, split the party, or befriend the villain
Required Inputs
Ask for these if not provided:
- System & level — which ruleset, party level, and number of players
- Length — a one-shot (single session) or the start of a campaign
- Tone — heroic, gritty, comedic, horror, sandbox
- The party — classes/archetypes if known, and any player preferences
- Boundaries — themes to include or avoid at the table
Framework: Structure With Room To Breathe
- Hook them fast. Open with a scene that gives the party a reason to act in the first ten minutes — not a tavern and a shrug.
- Set the table first. Session zero aligns tone and boundaries and introduces safety tools, so everyone's playing the same game.
- Outline beats, not a script. Plan the tent-pole moments and let the middle flex — players will surprise you.
- Scale the fights. Tune encounter difficulty to party level and size; give combats a twist (terrain, objective) so they're not just HP grinds.
- Prep to improvise. A short list of names, a rumor table, and "yes-and" fallbacks keep the game moving when players go off-map.
Output Format
[System] · level [X] · [N] players · [one-shot / campaign] · tone: [x]
Premise: [one-line pitch]. Hook: [why the party acts, now].
Session zero: tone [x] · boundaries [include/avoid] · safety tools [e.g. X-card] · expectations [scheduling, PvP, etc.].
First adventure
- Opening scene · 2. [beat] · 3. [beat/branch] · 4. [complication] · 5. Climax → [payoff/next hook].
NPCs: [name — want — voice] ×3. Encounters: [encounter — scaled to level/size — the twist] ×2–3.
If players go off-script: [improv fallbacks + a rumor/name table].
Quality Checks
- The hook gives the party a reason to act early
- Session-zero includes tone and content boundaries/safety tools
- The adventure is beats with branches, not a rigid script
- Encounters are scaled to the stated party level and size
- Improv fallbacks are provided for off-script play
Anti-Patterns
- A railroad that punishes players for not following the plot.
- Skipping session zero and blindsiding players with tone/content.
- Encounters that ignore party level — trivial or a TPK.
- All combat, no character — NPCs with no want or voice.
- No plan B for when players do the unexpected.
Example Trigger Phrases
- "Make me a D&D one-shot for four level-3 players, spooky tone."
- "Help me start a campaign — I've never DM'd before."
- "I need a session zero framework for my new group."
- "Give me a hook and first adventure for a heroic 5e party."
- "My players always go off-script — help me prep to improvise."