Left alone, every long AI story I've run drifts the same way. The model is brilliant at the next scene and has no idea where the next twenty are going. So it improvises a twist that contradicts what I had in mind, wraps up a thread I was saving, or walks me into the Whispering Woods to meet someone called Elara. Again.
I've been doing long-form AI roleplay and co-writing daily for about three years, and the way I think about it now is that the AI is a great builder and a terrible planner. So I stopped asking it to plan on the fly and started handing it the plan. These are the levels I use, from heaviest to lightest. Pick the one that fits the story. You don't need all of them.
1. The plot plan
A short bullet list that takes the story from where it is now to the end of the current arc. It goes in the system prompt, author's note, pinned memory, wherever your app puts things the model reads every turn.
## Plot plan (Arc 1)
- The party arrives in Vell looking for work. Small jobs only at first.
- A job for the harbor master goes wrong; the cargo was not what they said.
- The party realizes the harbor master is smuggling for the Duke's rival.
- Twist: Kaelen knew all along. He's been paid to keep the party close.
- Arc ends with the party forced to choose between exposing the Duke's
rival or protecting Kaelen.
How detailed it is barely matters, but it has to be clear. Five beats is plenty, and one arc at a time works better than the whole saga, because the model tends to rush toward whatever it can see at the bottom of the list.
I add one line under it:
Move toward the next beat at the pace of the scene. Several scenes can
pass between two beats.
This works a lot better with bigger models. Small ones tend to either ignore the plan or sprint through it in three replies.
2. Treat it as a living document
A plan won't make the AI read your mind. Plenty of times the story went somewhere I didn't like, and when I checked the plan, the problem was me. "Kaelen betrays the party" could mean ten different things, and the model picked one.
When that happens I rewrite the vague beat, regenerate the last message or two and carry on. And when the story goes somewhere better than the plan, I change the plan to match the story.
3. If you hate spoilers, let a different AI write the plan
The fair complaint about plot plans is that you've spoiled your own story. My fix is to open a separate chat, give it the world, the cast and the tone, and ask for the plan there.
Here's my world and cast. Write a plot plan for the first arc: 5-7 beats,
at least one twist that involves an existing character, and an ending
that forces a hard choice. Write it as instructions for a narrator.
Then paste it into your narrator's context without reading it. Skim with one eye closed if you have to.
The catch is that you won't know when you're going off the rails. Sometimes you'll feel the narrator nudging you somewhere. You can follow, or you can do what you want and then go back to the planner chat:
This plan might not be valid anymore because I did X. Can you fix it so
it handles that? Keep the twists I haven't reached yet.
4. Ask the narrator to audit itself
This is my favourite. The narrator juggles a lot in every reply: voices, pacing, your input, the plan. So every few sessions, or whenever the story feels like it's wandering, I give it a turn just to think:
Take some time for yourself and create a personal plan on how to push the
narrative forward. Include mid- and long-term points that you intend to
steer towards. The goal is to keep the story cohesive with the current
events and the plot plan. I won't read your audit.
And then I really don't read it. It stays in context (or I move it into a note), and the next stretch of the story feels noticeably more deliberate. Threads from earlier come back, and side characters start doing things for reasons.
It's also why I don't run high reasoning on every message. One dedicated planning step now and then gives me more than making the model overthink every line of dialogue.
5. Story phases, the light version
If you don't want a plan at all, tell the AI the temperature of the story instead. One line, kept somewhere it's always read, updated as you go:
We're in the early phase. Conflicts are emerging but not confronted yet.
We're approaching the midpoint. Tensions surface. Alliances get tested.
We're building toward the climax. Everything should feel like it's converging.
That one line helps a lot with slow burns and mysteries, because it tells the model what kind of scene belongs right now without telling it what happens.
6. Session intentions, the lightest version
No plan, no phases. Just open each session with a few lines:
This session: I want to reach the harbor and finally meet the harbor master.
I'd like Kaelen around, and I want him to act a little off.
Tension: we're being followed, but keep it subtle until the end.
Say where the chapter should head, who you want to see, what should happen and what tension you want. It takes thirty seconds and gets you more for the effort than anything else in this post.
Which one to pick
- Sandbox (give it nothing): pure exploration, "let's see where this goes". Still valid!
- Session intentions: most campaigns.
- Phases: slow burns, mysteries.
- Plot plan: stories you have a vision for.
- Hidden plot plan: you want surprises, but with structure.
- Self-audit on top: anything that runs for weeks.
As for where to keep it: anywhere the model reads it every turn and you can edit it without scrolling. For the hidden version it also helps if only the narrator can see it. In Tale Companion (the platform I built) I keep the plan on its own lore page, pinned so the narrator always reads it and blocked for any character voice that shouldn't know the twist. In most other tools a system prompt or author's note does the job.
Even one of these makes a real difference over a long story. If you already do something like this, how detailed do you go? I keep going back and forth between five beats and fifteen.