How to Fix AI Pacing When Your Draft Sprints
You asked for the scene where Idris finds his sister's name on the customs manifest. What came back was 1,150 words, and by word 900 he had found the manifest, walked across the harbor district, put it on Nezha's table, listened to her explain herself, and forgiven her.
An afternoon. The whole thing, start to finish, in an afternoon.
You had three chapters planned there. The finding, the four days of not-saying-anything, the conversation on the pier that goes wrong in a way neither of them expected. Instead you have a plot summary with dialogue in it, and the worst part is that nothing in it is badly written. The sentences are clean. It just refuses to let anything sit.
Why AI rushes your story
AI rushes because it was trained to be helpful, and helpful means resolving things. A conflict on the page reads to the model as a problem awaiting a solution, so it supplies one — usually before the scene ends.
A writer running long-form projects for two years put it precisely in an r/WritingWithAI breakdown that struck a nerve: "AI wants to resolve everything. Immediately. In the same scene it was introduced." Their example is almost exactly the manifest problem — a character discovers a betrayal, confronts the betrayer, has the emotional conversation, and moves on, all inside one reply. "Three sessions of story compressed into fifteen lines."
The thread filled with people who recognized it instantly. One commenter said the post "wrote about everything I didn't like with scenes AIs prepared for me, but I couldn't put into words what actually felt wrong." Another described what they actually wanted: "a 'yes, and…' writing partner not a 'you're done.' Bot."
So this isn't a prompting skill issue, and it isn't your model being bad at prose. It's an incentive mismatch: the model optimizes for a finished-feeling answer, and you're writing a book, where the whole pleasure is deferral.
The craft name for what's missing: the sequel
Your draft isn't missing scenes. It's missing sequels — and once you know the term, you can ask for the thing directly.
The structure comes from Dwight Swain. Writers Helping Writers notes that "Scene and Sequel is a technique developed by Dwight Swain in his book, Techniques of the Selling Writer," and it splits fiction into two alternating units. A scene is an action unit: your POV character wants something specific, hits obstacles, and ends the unit worse off than they started. A sequel is the reaction unit that follows — the character absorbs what just happened, faces the new dilemma it created, and finally makes a decision, which becomes the goal driving the next scene.
That last link is the engine. As Writers Helping Writers puts it, "the decision will lead us into our next scene, where the character(s) develop a new goal."
Here's the thing that matters for pacing: the sequel is where your pace lives. Dabble's breakdown of the pattern observes that sequels "typically bring a sense of stillness" and slow the narrative through reflection, while "a long string of back-to-back obstacles… will speed things up."
Which gives you the diagnosis in one line: AI writes scenes and skips sequels. It will happily generate goal, conflict, and disaster. But instead of giving Idris four days to carry the manifest around in his coat pocket, it jumps straight to the next action unit, and because the reaction never happened, his decision to confront Nezha arrives unearned. The scene isn't too short. It's unaccompanied.
Cap the scope, not the word count
The instinct is to ask for fewer words. Don't — cap what's allowed to happen instead, and let the word count land where it lands.
Word limits can actually make rushing worse. A commenter in an r/WritingWithAI thread on slowing down progression pushed back on the standard advice directly: hard limits "can actually cause rushing… If you tell it '500 words' and give it multiple beats, it'll often either cram everything together or cut a scene off mid-moment." Give a model five beats and a 500-word ceiling and you've asked it to speedrun. It will comply.
The fix in that same thread: "What works better for pacing is controlling scope, not length. Give it fewer beats at a time and explicitly tell it to stop." The shape of the instruction becomes write a single scene where X happens, end the scene once this moment resolves, don't advance the plot past this point.
Try it on the manifest. Instead of "write the chapter where Idris finds the manifest and confronts Nezha," run four requests:
Beat one, the discovery. Idris is alone in the customs office after hours, looking for something else entirely. He finds her name. Nothing else happens — he does not leave the building, he does not decide anything. Call it 800 words, and it ends on the disaster, where it should.
The sequel. Three hundred and fifty words of Idris walking home the long way, reasoning badly in circles. No new information, no plot. This is the unit AI never volunteers, and the one that makes everything after it land.
Beat two, four days of nothing. Six hundred words across two brief passes: the siblings have dinner twice, neither mentions it, and the manifest is in his coat both times.
Beat three, the pier. Nine hundred words. Now the confrontation, and now it costs something.
That's roughly 2,650 words and four days of story where the single-prompt version gave you 1,150 words and an afternoon. Same events. The difference is entirely in what you refused to let the model resolve.
This means generating at scene resolution instead of chapter resolution, which is easier somewhere your story is already broken into acts, chapters, and scenes rather than in one long chat — what NovelMage's Story Planner and scene-level generation are for. It also means four or five calls where you used to make one, which is the quiet argument for running a local model through Ollama or LM Studio: iterate twenty times on a stubborn sequel and you're spending electricity, not credits.
One honest caveat: if you write fast-moving serial fiction where readers are paying for plot velocity, don't over-apply this — some genres want the sprint, and a 350-word interiority passage is exactly what your reader skims.
Don't show it the whole outline
Show the model only the next two or three beats. If it can see where the story ends up, it will try to get there.
This was the single most useful thing in that thread, from a commenter who'd clearly been fighting it a while: "never show it your entire outline at once. I only show the next 2–3 beats, tops. If it can see the destination, it will sprint."
It's counterintuitive, because we're all told to give models more context, not less. But context about your world and context about your destination do different jobs. Feed it your characters, your continuity, your voice. It does not need to know that Nezha confesses in chapter twenty-two — give it that, and every scene between here and there starts leaning toward the confession.
This is a different failure from the model losing track of details it was never given — that one's about what's actually in the context window when a chapter gets generated. Pacing is the opposite problem: too much foresight, not too little memory.
A beat sheet is the right tool here precisely because you can hold most of it back. You know the shape. The model gets the next two rows.
Protect the threads that are supposed to stay open
State explicitly which conflicts do not resolve in this scene. Models respect that instruction well — they just never infer it.
The r/WritingWithAI guide frames it as keeping a list of what should stay messy: "The tension between Mira and Kael is NOT resolved in this scene. They're still circling around the issue." "The mystery of the missing letters should deepen, not get answered." One commenter had sharpened it into a line worth stealing: this scene only sets up emotional debt, we are not allowed to cash it in.
Two more instructions from the same guide that do real work:
Complicate, don't resolve. Every scene should make things worse or make them different — not better. Told plainly to the model: "when a problem arises, add a complication rather than a solution," and "success always comes with a cost or a catch."
Yes, but / no, and. Borrowed from tabletop RPGs. When a character attempts something, the outcome is either yes, but something new surfaces, or no, and something else degrades too. Clean success and clean failure are both dead ends. Ban them and the story stops needing you to push it.
The related move is planting things you don't pay off yet — a detail that means nothing now and everything in chapter thirty. Models almost never do this unprompted, which is its own recurring problem: the rifle gets described and never fired. Ask for one out-of-place detail per scene and note where you put it.
Vary the tempo on purpose
Slow isn't the goal. Contrast is. As the guide puts it: "Fast-fast-fast is exhausting. Slow-slow-slow is boring."
Pacing is a rhythm you author, not a speed you set. So label each request with its tempo: this scene is a breath — slow, character-focused, no plot advancement. Then: now things speed up, short sentences, quick cuts between locations. Then: this conversation should feel long and uncomfortable; don't rush to the point.
That third instruction needs backup, because a model asked for a long uncomfortable conversation will often write a long conversation that summarizes discomfort rather than staying inside it. Sequels are where prose flattens into report-writing fastest — there's no plot event to hide behind. Idris walking home has to carry itself on interiority alone, so specify that: stay in his head, no time skips, he does not reach a conclusion.
A practical habit: after any high-tension sequence, deliberately request a quiet one. Not because the story demands it — because you demand it, and you're the architect. The model, as the guide says, is a great builder and a terrible planner. Pin the standing rules somewhere the model always sees them (slow pacing, interiority over plot, no time skips unless told) and you stop re-typing them on the fifteenth generation of the night.
Frequently asked questions
Why does AI rush through scenes even when I tell it not to?
Because "don't rush" doesn't constrain anything the model can measure — it follows scope limits far better than tone requests. Replace it with "write only Idris finding the name; end the scene there; do not let him leave the office," and compliance changes dramatically. Constrain events, not pace.
Should I use word counts at all?
As a rough expectation, yes. Writers in those threads described beats landing anywhere from 400–600 words up to about 1,000, and knowing your own range helps you notice when a reply crammed too much in. But set scope first and treat length as the output — a word count paired with too many beats is the recipe for the exact compression you're trying to fix.
Is this a model problem? Would a different model rush less?
Marginally. Default verbosity and tempo differ between models, and the consensus in these threads is that trying the same prompt across a few is the only way to learn which default voice you like. But every model shares the resolve-the-conflict instinct, because every model was trained to be useful. Switching models changes the flavor of the rushing, not the rushing.
How do I fix pacing in a draft that's already written this way?
Find every place where a conflict was introduced and resolved in the same scene — that's the audit. For each one, cut at the disaster and write the sequel yourself: reaction, dilemma, decision, in that order. You usually don't need to rewrite the confrontation, just delay it. Most rushed drafts need insertion, not replacement.
The short version
Your model isn't writing too fast. It's writing half the pattern — action units with the reaction units stripped out — which is why a betrayal discovered in paragraph four gets forgiven by paragraph nine without anyone feeling anything. Give each request one beat, say what isn't allowed to resolve, keep the ending out of its sight, and write the sequels on purpose.
If you'd rather do that in a workspace built around acts, chapters, and scenes than in a chat window — with your manuscript staying on your own machine and local models making beat-by-beat iteration cost nothing per call — NovelMage is a one-time $99.99 license good on three devices, with a 7-day free trial that doesn't ask for a card.
Go find the last scene where somebody forgave somebody too fast. The fix is three hundred words of walking home.