The Worldbuilding Contradiction Auditor: Catch Continuity Errors Before Readers Do
Why this prompt matters
Continuity errors in published series don't get caught by editors who haven't memorized 200,000 words of prior books — they get caught by readers, publicly, in Goodreads reviews and Reddit threads that outlive the book itself. Once a series is in print or live online, a contradiction can't be quietly fixed; it becomes errata, or worse, the detail readers remember instead of the plot. Catching it at the draft stage, before a single reader sees it, is the only point where the fix is free.
What we use it for
You're drafting chapter 14 of book four in a fantasy series, eight months after you last reread book two. You just wrote a tense confrontation scene where your protagonist casts a spell from across a crowded tavern — but somewhere in notes from eighteen months ago, you're almost certain you established that magic in this world requires physical contact with fire or living wood. You don't remember exactly where you wrote that, or how strictly you meant it.
Prompt
Role: You are a meticulous continuity editor for long-form fiction. You have read every entry in this series multiple times and track internal consistency obsessively — magic/technology rules, geography, timelines, and character backstories. Context: [PASTE YOUR WORLDBUILDING NOTES: established rules, facts, timeline, character histories — as much as you have] [PASTE THE NEW SCENE OR CHAPTER DRAFT you want checked] Task: Compare the new scene against the established worldbuilding notes. Identify every place where the new scene contradicts, strains, or is ambiguous against an established fact. Constraints: - Do not comment on prose style, pacing, or dialogue quality — only continuity and factual consistency - Distinguish "Definite Contradiction" (directly violates an established fact) from "Worth Checking" (plausible tension that may or may not be intentional) - For every flagged item, quote or closely paraphrase the specific established fact being tested, and quote the specific line in the new scene that creates the issue - Do not suggest how to fix anything unless I ask — your job is to flag, not rewrite - If you are not given enough worldbuilding context to judge something, say so explicitly rather than guessing - Ignore minor numerical details (e.g., "a few days" vs "three days") unless the discrepancy is load-bearing for the plot Output format: 1. Numbered list of flagged issues, each with: [Severity: Definite Contradiction / Worth Checking] — [Established fact] vs [New scene detail] — [one-sentence explanation of why it's a problem] 2. A closing verdict: "Safe to publish as-is" / "Needs author review before publishing" / "Needs explicit revision"
Result
Example run (worldbuilding notes included: "Magic in Vendrathi requires the caster to be in physical contact with either open flame or living wood; attempting to cast without contact causes the spell to misfire or backfire (established Book 1, Ch. 7, reiterated Book 2, Ch. 19 when Kaelen is injured attempting a contactless cast). Kaelen lost two fingers on his left hand in that incident and has avoided fire-based casting since." New scene excerpt: "Kaelen raised his hand toward the far end of the tavern and the air crackled; the chandelier above the bar burst into flame, and three men went sprawling as the blast hit them.")
1. [Severity: Definite Contradiction] — Established fact: magic requires physical contact with open flame or living wood to cast (Book 1, Ch. 7; reaffirmed Book 2, Ch. 19). New scene: Kaelen casts a fire spell at "the far end of the tavern" with no contact described — he is not touching the chandelier, a flame, or living wood. This directly violates the core rule of the magic system, not a minor detail.
2. [Severity: Worth Checking] — Established fact: Kaelen lost two fingers on his left hand in Book 2, Ch. 19, and has specifically avoided fire-based casting since that injury. New scene: Kaelen performs a large-scale fire spell with no mention of hesitation, pain, or the missing fingers affecting the casting gesture. Even if contact were restored to the scene, this emotional and physical throughline from his injury appears to be missing. Worth confirming whether this is an intentional turning point (Kaelen overcoming his fear) or an oversight.
3. [Severity: Worth Checking] — No established rule found regarding range or line-of-sight once contact is made. If you intend for Kaelen to touch a flame and then project the effect across the room, this would be a new rule you're introducing — worth flagging that this expands the magic system beyond what Books 1–2 established, which attentive readers may notice.
Verdict: Needs explicit revision. The scene as drafted contradicts the core contact-casting rule established across two books. If you want this scene to stand, either show Kaelen touching a flame source first, or treat this as a deliberate escalation of his abilities and set it up explicitly.
Long-running fiction has a specific kind of failure mode that doesn't show up in a first-draft critique: the contradiction that only becomes visible once you're 400 pages past where you set the rule. The Worldbuilding Contradiction Auditor is built to solve exactly that — not generate ideas, not fix prose, just catch the moments where a new scene quietly breaks a rule the author forgot they wrote.
Why the prompt is structured this way
The Role instruction asks the model to behave as a continuity editor rather than a general critic, which matters because most AI feedback on fiction defaults to commenting on prose style and pacing — exactly what this prompt explicitly rules out in the Constraints section. Separating "continuity checking" from "writing feedback" keeps the output focused and prevents the model from burying a real contradiction under ten paragraphs of stylistic suggestions.
The Context section asks for two separate inputs — the worldbuilding notes and the new scene — rather than one combined document, because the model needs to treat the notes as ground truth and the scene as the thing being tested against it. This separation is what lets the model cite a specific established fact when it flags a problem, instead of vaguely gesturing at "this feels off."
The two-tier severity system (Definite Contradiction vs. Worth Checking) is the most important design choice in the prompt. Without it, an AI continuity check tends to either overwhelm the writer with every minor inconsistency it can find, or stay silent on anything it's not fully certain about. Forcing a severity label makes the model commit to a judgment call rather than hedging everything, while still leaving room for genuinely ambiguous cases.
The instruction not to suggest fixes is deliberate. A writer asking "did I break my own rule?" and a writer asking "how do I fix this scene?" are two different requests, and conflating them means the model spends its attention on rewriting instead of verifying. If the audit flags a real contradiction, the author can run a separate, focused prompt to fix it — but fixing and flagging shouldn't happen in the same pass, because a model eager to "solve" the problem will sometimes paper over a contradiction instead of clearly naming it.
How to get the most out of it
This prompt is only as good as the worldbuilding notes you paste in. If your notes are thin, say so up front, or the model will either guess — which it's instructed not to do — or miss contradictions that exist only in your head and never made it onto the page. For a series with an actual worldbuilding bible, even a messy one in a Notion doc or a Word file, this prompt pays for itself the first time it catches a magic-system violation or a timeline slip before an editor or a reader does. Run it on every new chapter against your full accumulated notes, not just the most recent book, since the contradictions that slip through are usually the ones from several books back.