Six Ways to Use AI in Campaign Prep Without Losing Your Voice

AI is most useful in campaign prep when it handles the work that slows you down without touching the work that defines your world.

The distinction matters. Summarising last session's notes is overhead. Deciding what the villain wants is creative. AI belongs in the first category. The second stays yours.

Here are six uses that consistently deliver without getting in the way.

1. Turn messy session notes into a clean recap

You know the notes. Half-sentences. Abbreviations only you understand. A name scrawled in the margin with no context. After a long session the last thing you want to do is rewrite them into something readable.

Ask the Lore Oracle to turn your raw notes into a structured recap. It can produce a clean summary organised by event, NPC interaction, or location — whatever format you use. The result is a draft. You trim it, correct anything the Oracle misread, and file it in the session log.

What you save: thirty minutes of post-session admin. What you keep: the judgement call about which details matter.

2. Expand a minor NPC from three lines of notes

You have a throwaway NPC who unexpectedly became interesting. The players spent forty minutes talking to a dockworker you invented on the spot. Now they want to meet him again next session and you have nothing on him except a name and a vague sense of suspicion.

Ask the Oracle to expand him using what is already in your vault — his district, its controlling faction, the recent events that would have shaped someone in his position. The Oracle drafts an entry: background, motivation, potential role. You edit it, cut what does not fit, and accept what does.

What you save: the cold-start problem of building from nothing. What you keep: the final version of who he actually is.

3. Generate names that fit your world's conventions

Generic fantasy names are one of the fastest ways to break immersion. If your setting has a specific cultural logic to its naming — syllable patterns, prefixes tied to region or faction, sounds that signal origin — a generic name generator ignores all of it.

Give the Oracle examples of existing names in your vault and ask for variants. It works from the pattern rather than from a default fantasy name list. You still choose the one that sounds right, but the options are grounded in your world rather than pulled from nowhere.

What you save: the twenty minutes of trying to invent a name that sounds like it belongs. What you keep: the final choice.

4. Surface unresolved threads across your session log

Long campaigns accumulate loose ends. A contact who was promised a favour. A rumour that was planted and never followed up. An NPC who knows something the players never thought to ask about.

Ask the Oracle to scan your session log and surface threads that appear to be unresolved. It cannot tell you which ones matter — that is your call — but it can pull them out of a log that is now forty sessions long and impossible to read end-to-end before every prep.

What you save: the archaeology of reading back through everything. What you keep: the decision about which threads are worth picking up.

5. Turn saved entities into art prompts

You want a reference image for a faction's headquarters, a key NPC, or a location the players are about to reach. The problem with writing art prompts from scratch is that they tend to drift toward generic — you describe what you imagine, but the specific details that make it yours get vague.

Ask the Oracle to draft a prompt using the entity's saved description, its faction ties, its regional context, and any visual details already in the notes. The prompt comes out specific rather than generic because it is drawing from your vault rather than from whatever the model defaults to.

What you save: the translation work of turning notes into a prompt. What you keep: your world's visual logic.

6. Revise an existing entry with specific corrections

The Oracle is not just for generating from scratch. You can hand it an existing entity entry and tell it what to change.

Examples:

• "This NPC's motivation needs to shift after the events of session 22 — update accordingly."
• "This faction description is accurate but the tone is wrong — rewrite it harder and more paranoid."
• "Add a flaw. Keep everything else."

The Oracle revises the entry as a draft. You review what changed, accept the parts that landed, and discard what did not. Your existing lore stays intact until you decide otherwise. You are directing an edit, not handing over authorship.

This is particularly useful when a campaign event changes something established — a character's allegiance shifts, a location is destroyed, a secret is revealed. Rather than rewriting the whole entry yourself, you describe what changed and let the Oracle produce a starting point.

What you save: the friction of rewriting established lore after campaign events. What you keep: control over what changes, what stays, and what becomes canon.

None of these replace the creative decisions. They reduce the friction around them. The session still needs a plot. The NPC still needs a reason to matter. The names still need to feel right to you. The Oracle handles the overhead. The authorship stays where it belongs.

Part of the Codex Cryptica responsible AI series:

1. The Lore Oracle Is Not the Author
2. A Worldbuilding Tool Should Still Work Without AI
3. Why Worldbuilding AI Should Know Your Lore Before It Speaks
4. Drafts Are Not Canon
5. Six Ways to Use AI in Campaign Prep Without Losing Your Voice (this article)
6. AI Slop Happens When the Tool Has No Memory
7. Revising Your Lore with the Oracle