A 30-page guide is not one prompt — it is a small project. Trying to one-shot an eBook produces a saggy, repetitive draft that nobody finishes. The professional method is "outline first, then write the outline." This tutorial gives you the prompt sequence to do exactly that without losing voice, coherence, or your sanity.
Long-form content — eBooks, whitepapers, definitive guides, ultimate-this and ultimate-that — has a unique failure mode: the middle chapters get mushy. AI starts strong, drifts by chapter three, repeats itself by chapter five, and forgets the original thesis by chapter seven. The fix is structural. You break the work into stages, prompt each one separately, and never ask AI to write more than 800–1000 words at a time. This tutorial walks through the four-stage workflow that long-form writers swear by.
Long-form AI writing breaks into four stages: thesis, outline, chapter drafting, and continuity pass. Each stage uses a different prompt, and each stage's output feeds the next.
Think of it like building a house. The thesis is the architect's brief — what is this house for? The outline is the floorplan — how many rooms, where do they go, how do you walk through them? The chapter drafts are the rooms themselves — walls, flooring, lighting. The continuity pass is the walk-through — making sure light switches are where you expect, the kitchen flows to the dining room, no stairs go nowhere. Skip the floorplan and you end up with a beautiful kitchen attached to a closet.
Weak prompt
Write a 10,000-word eBook about productivity for freelancers.
Even if the AI complies, the output will repeat the same three ideas across ten chapters, slip in and out of voice, and lose the central argument by the halfway point. Long-form is a structural problem — and you cannot solve a structural problem with one giant prompt.
Use one prompt per stage. Each one is small, focused, and reusable. Here is the sequence for an eBook titled "The Calm Freelancer".
Stage 1 — Thesis prompt
Act as a senior non-fiction book editor.
Help me articulate the thesis for a short eBook
called "The Calm Freelancer" — for solo freelancers
who feel chronically behind on work.
Return:
- A one-sentence thesis (the core promise)
- Three things this book argues that others don't
- One sentence describing the reader's life after
finishing the book
Stage 2 — Outline prompt
Using the thesis below, write a chapter outline
for a 12,000-word eBook.
[paste thesis from Stage 1]
For each chapter, return:
- Chapter title (under 8 words)
- One-line chapter promise
- 4–6 bullet sub-sections
- The single most important sentence the reader
should remember from that chapter
Aim for 7–9 chapters. Each chapter should have
a clear job in the overall argument — no filler.
Stage 3 — Chapter draft prompt (run once per chapter)
[paste BRAND VOICE PROFILE from Topic 6]
Now draft Chapter 3 — "The Two-Lane Inbox".
Use this outline:
[paste the chapter outline section from Stage 2]
Constraints:
- 1,200 words
- Open with a single-sentence hook
- Use one short story or scenario halfway through
- End with a one-paragraph summary that names
the chapter's most important sentence
- Match the rhythm in the voice profile
- Use British spellings (organise, behaviour, optimise)
Stage 4 — Continuity prompt
Below are chapters 1 through 7 of "The Calm Freelancer".
[paste each chapter]
Audit for:
1. Repeated ideas across chapters (list with chapter numbers)
2. Tone drift (any chapter that sounds different)
3. Continuity holes (anything promised but not delivered)
4. The strongest single sentence in the book
5. Three sentences that should be rewritten or cut
Return your audit as a short numbered report.
This four-stage workflow produces a coherent, on-voice manuscript. Each prompt is small enough to fit comfortably in the model's working context, and each one builds on a checked, polished previous stage. The total writing time is shorter, the result is significantly better, and the editing pass is a true edit rather than a rescue mission.
Tip: For whitepapers, add a "facts and figures" stage between the outline and the draft. List the statistics, case studies, and citations you intend to use. Without this stage, AI invents numbers — which is fatal in a B2B document.
Pick a topic you know deeply and run Stage 1 and Stage 2 only. You should end with a thesis you believe and an 8-chapter outline you would actually read. Treat this as the deliverable — most long-form projects fail because the outline never got tight enough.
Take one chapter from a long-form piece you wrote previously (without AI). Run the Stage 4 continuity prompt against it. Notice which issues AI catches that you missed.
Convert a 5-chapter outline into a "lead magnet" guide: 3,000 words instead of 12,000. Use the same workflow but keep each chapter draft to 600 words. Watch how the workflow scales down as cleanly as it scales up.
Sign in to join the discussion and post comments.
Sign inAdvanced Prompt Engineering Techniques
Master the powerful techniques AI experts use every day. Chain-of-thought, RAG, agents, function calling, prompt evaluation, and much more — 20 deep-dive tutorials.
Prompt Engineering for Education & Learning
Use AI as your personal tutor. Learn how to study faster, create lesson plans, generate practice questions, master languages, and prepare for competitive exams with smart prompts.
Prompt Engineering Projects & Real-World Applications
Twelve hands-on projects that turn prompt engineering theory into a portfolio. Build chatbots, content generators, RAG systems, and more.
Prompt Engineering for Data Science & Analytics
Supercharge your data workflows with AI. 15 practical tutorials on using prompt engineering for data cleaning, EDA, machine learning, SQL, visualisation, and more.
Prompt Engineering for Specific AI Tools
Tool-by-tool mastery — deep dives into ChatGPT, Claude, Gemini, GitHub Copilot, Midjourney, Stable Diffusion, and more. Learn the exact prompting techniques each platform rewards.
Prompt Engineering for Developers
Use AI as your coding co-pilot. 18 tutorials on writing prompts to generate clean code, debug faster, write tests, build APIs, and ship better software.