AI Prompts for Novel Writing: A 90,000-Word Case Study

Below is my story bible (facts that must stay consistent) followed by Chapter 21.
Do not rewrite the chapter. Instead, list every place where Chapter 21 contradicts
or strains against the bible. Then list any fact in Chapter 21 that SHOULD be added
to the bible because it's new canon.
[STORY BIBLE]
---
[CHAPTER 21]

Can AI actually help you write a whole novel — not a chapter, not a scene, but ninety thousand words that hang together — without turning your book into gray paste? That's the question every novelist asks the moment they open ChatGPT, and most of the answers online are either breathless hype or flat dismissal. The truth sits in between, and it's more useful than both.

This is a walk-through of how ai prompts for novel writing succeed and fail across a full manuscript, built from a composite of workflows I've seen writers actually use.

The Problem the Novelist Faced

Meet the writer: a project manager writing her first novel in stolen hours, a literary thriller at roughly 90,000 words. Her problem wasn't prose — she wrote clean sentences. Her problem was scale. By chapter 20 she couldn't remember whether she'd already revealed the detective's brother was dead. Her subplots drifted. A character's eye color changed twice. The book was collapsing under its own length, and she was spending more time re-reading than writing.

She turned to AI hoping it would help her hold the whole thing in mind at once. Reasonable hope. Her first approach was a disaster.

The Wrong Approach

She fed the model chapter after chapter and asked it to "continue the story." For about a week it felt magical — pages appeared. Then she reread them.

The AI's chapters were smooth and utterly generic. Her tense, specific detective became a stock noir figure. The dialogue lost its edges. Worse, the model kept quietly contradicting established facts because it couldn't hold 60,000 prior words in memory — it only saw what she pasted. She spent a month writing, then a second month deleting most of it. Net progress: negative.

⚠️ Common mistake: Using AI as a continuation engine on a long project. Models don't have your whole book in their head; they have whatever's in the current context window. Ask one to "continue" and it invents a plausible average, not your story — and it will cheerfully contradict chapter 3 because it never saw chapter 3. On novel-length work this doesn't save time. It manufactures cleanup.

The Correct Prompt

The fix was to stop asking the AI to write and start asking it to remember and check. She built a story bible — a plain document of facts, timelines, and character details — and used prompts like this:

Below is my story bible (facts that must stay consistent) followed by Chapter 21. Do not rewrite the chapter. Instead, list every place where Chapter 21 contradicts or strains against the bible. Then list any fact in Chapter 21 that SHOULD be added to the bible because it's new canon. [STORY BIBLE] --- [CHAPTER 21]

What this does: It turns the model into a continuity editor with perfect patience. It catches the dead brother resurfacing and the shifting eye color, and it keeps the bible current so the next chapter has a clean reference.

She paired it with a structural check she ran every five chapters:

Here are one-line summaries of my last 5 chapters. For each, rate the tension 1-10 and name whose goal drives the scene. Then tell me: is any subplot going quiet for too long? [SUMMARIES]

What this does: It gives her a bird's-eye view of momentum across the book — the thing that's impossible to feel when you're buried in a single scene.

⚡ Pro tip: Keep the story bible in a separate file and paste it fresh into each session. The model has no memory between chats; your bible is its memory. A stale bible is worse than none, because it checks against the wrong facts.

Results and What Changed

Once she stopped outsourcing the writing and started outsourcing the bookkeeping, the manuscript stabilized. Continuity errors dropped to near zero. She finished the draft in four months instead of the projected nine, and — this is the part that matters — it still read like her book, because every sentence was still hers.

⚡ Pro tip: Ask the model to summarize each chapter in your voice right after you write it, then save those summaries. They become both your synopsis-in-progress and the input for structural checks. Two birds, one habit.

How to Apply This to Your Situation

You don't need to be at 90,000 words to start. From chapter one, keep three living documents: a facts bible, a timeline, and a one-line-per-chapter summary. Feed the relevant one into any AI check. The discipline of maintaining them is half the benefit — it forces you to know your own book.

If you're a discovery writer who hates outlines, use AI after each chapter, not before. Let it map what you unconsciously built, so you can see your structure emerging without planning it to death.

If you're a plotter, use it before drafting to stress-test your outline: "Where in this outline does the protagonist stop making choices and start reacting? That's usually a soggy middle."

The Timeline Trap Nobody Warns You About

There's a specific failure that hits long manuscripts around the two-thirds mark: the timeline quietly breaks. A character mentions "last week" but the events were three days apart. A season shifts without cause. These errors are invisible while drafting and glaring to readers.

A timeline check catches them:

Below are dated or time-referenced events from my manuscript in the order they appear. Build a strict chronology and flag any contradiction — anything that can't physically fit the stated timeframes. [LIST OF TIMED EVENTS]

What this does: It turns scattered "three days later" and "that winter" references into a single spine and shows you where the spine snaps.

⚡ Pro tip: Track time in a plain column as you draft — chapter, in-story date, days elapsed. It feels like overhead for about a week, then it saves you a brutal untangling later. The writers who skip this are the ones rewriting act three at midnight, hunting a phantom Tuesday.

A Prompt for the Sagging Middle

Nearly every long manuscript sags in the middle, and it's rarely a prose problem — it's a momentum problem. Diagnose it directly:

Here are one-line summaries of my middle third (chapters 8-16). For each, tell me whether the protagonist is DRIVING events or REACTING to them. If she's reacting for more than two chapters straight, tell me where to hand her back the wheel. [SUMMARIES]

What this does: Sagging middles are almost always stretches where the hero stops choosing and starts getting pushed around. This finds the exact chapter where agency drains out.

⚡ Pro tip: A quick test for any middle chapter — does the protagonist end it having made a decision that closes off other options? If she can still do anything, the plot hasn't tightened, and readers feel that slack even when the writing is clean.

Why the Story Bible Beats a Longer Context Window

You might think a model with a huge context window removes the need for a bible — just paste the whole book. In practice, pasting 90,000 words every session is slow, expensive, and the model's attention thins across that much text; it starts missing things buried in the middle. A tight bible of 800 words gives it exactly the facts that must stay consistent, with none of the noise. Curation beats brute force. The discipline of deciding what belongs in the bible is also the discipline of knowing your own book cold.

Next Steps

Start your bible today, even mid-draft. Run one continuity check on your last chapter using the prompt above and see how many things it catches. I'd bet it's more than zero.

The catch with a system like this is that it only works if the prompts are always at hand — a continuity check you have to rebuild from scratch is a check you'll skip. Store your novel-writing prompts in PromptABCD, grouped into a "novel toolkit" you can pull up per chapter. The bible check, the structural audit, the voice-summary — one place, one click, every writing session. That consistency is what carries a book across ninety thousand words.