Story Outline Builder
A chapter-level outline you can draft from, with outcomes and thread tracking.
Builds a scene-level outline from a premise: a nine-beat shape, chapters with point of view, goal, conflict and a yes-but or no-and outcome, word counts, a thread map of every story question, and the chapters that currently have no engine.
Ready-to-use prompt
The prompt
Copy it as-is, then swap the bracketed placeholders for your own details before running it.
Role: You are a developmental editor producing a draftable outline.
Context:
- Premise and ending, if known: {{premise_and_ending}}
- Protagonist, antagonist and supporting cast: {{cast}}
- Point-of-view structure and tense: {{pov_structure}}
- Target length and chapter count: {{length}}
- Scenes already written or fixed: {{existing}}
Task: Return the outline in three passes.
1. Shape: the story in nine beats, one line each, ending to ending.
2. Chapters: for each chapter give point-of-view, location, the goal pursued, the conflict met, the outcome as yes-but or no-and, and the approximate word count.
3. Threads: every subplot and story question, the chapter it opens in, the chapters it appears in, and where it closes.
Then analyse:
- Chapters with no goal or no change; these are the drafting hazards.
- Long stretches without the antagonistic force present.
- Threads opened and never closed, and threads closed too early.
- Point-of-view balance if multiple viewpoints are used.
Rules:
- Every chapter outcome must be yes-but, no-and, or no. Straight successes need a justification line.
- Do not invent subplots that the stated cast cannot carry.
- Respect existing scenes; mark where the outline must bend around them as FIXED.
- Keep chapter summaries under sixty words.
Finish with: the three chapters most likely to be cut in revision, and what to move out of them first.Estimated results
Editor's note
Why this prompt matters
An outline that lists what happens is not draftable. What makes a chapter writable is knowing whose viewpoint it is, what they are trying to get, what stops them, and how it ends badly enough to force the next chapter. This prompt requires all four, and constrains every outcome to yes-but, no-and or no, which surfaces the chapters that quietly have no engine before you spend a month writing them. The thread map runs in the same pass because retro-fitting subplots into a finished draft is one of the most expensive revisions there is, and a table of what opens where makes it nearly free.
Anatomy
Prompt engineering breakdown
Role
Context
Goal
Constraints
Output format
What you'll get
Expected output
A nine-beat story shape, a chapter table with viewpoint, location, goal, conflict, outcome and word count, a thread map of every subplot and story question with open and close points, plus a diagnosis of chapters with no change, antagonist-free stretches, unresolved threads and viewpoint balance.
Under the hood
Why this prompt works
Restricting outcomes to yes-but, no-and or no is a small constraint with a large effect: it makes chapters causally linked rather than sequential, so each one creates the pressure that starts the next. Tracking threads alongside chapters catches the two failures that only appear at the end — questions opened and forgotten, and subplots closed so early the last act has nothing left to resolve. Flagging fixed scenes keeps the outline compatible with pages already written.
Model fit
Best AI models for this prompt
ChatGPT
Best default. Handles long chapter tables without losing consistency.
Claude
Better at thread tracking and at flagging chapters where nothing changes.
Gemini
Useful when partial drafts are pasted in and folded into the outline.
When to use
- Planning a novel, novella or serialised story.
- Rescuing a stalled draft by mapping what exists and what is missing.
- Working to a deadline where pacing must be planned.
When not to use
- For discovery writers who lose momentum when the plot is known.
- For short fiction where a beat sheet is enough.
- When the premise itself is unresolved.
Get more from it
Pro tips
- 1
Outline to the ending even if you will change it; the shape matters more than accuracy.
- 2
Fix engineless chapters at outline stage, not in month three of drafting.
- 3
Track threads in the same pass — retro-fitting subplots is far more expensive.
- 4
Keep one outline file and update outcomes as you draft.
Don't ship this
Common mistakes
✗ Summarising events instead of specifying goals.
Fix — Require viewpoint, goal, conflict and outcome for every chapter.
✗ Chapters that end in straight success.
Fix — Force yes-but or no-and outcomes unless a success is justified.
✗ Adding subplots the cast cannot carry.
Fix — Restrict threads to the stated cast and check the thread map.
People also ask
Frequently asked questions
Q.Will outlining kill my momentum as a discovery writer?
It can. If knowing the ending removes your reason to write, use only the nine-beat shape pass and skip the chapter table, or run the outline after a messy first draft as a diagnostic.
Q.Why must chapters end in yes-but or no-and?
Because that is what links chapters causally rather than sequentially. A chapter ending in clean success gives the next one no pressure to start from, which is where drafts stall.
Q.Can I outline around scenes I have already written?
Yes. List them in the existing scenes field and the outline bends around them, marking each accommodation as fixed so you can see what the structure is paying for them.