A strong book series needs two levels of planning: the story inside each volume and the larger arc connecting all of them. You can use Nellie to generate complete books from detailed prompts, but you should maintain the series-level source material yourself.
That distinction matters because Nellie’s dedicated multi-part series feature is not currently listed as available. The Nellie FAQ describes it as coming soon. For now, plan each installment as a separate book, supply the relevant series information in every prompt, and check the resulting manuscript against a shared series bible.
This is Nellie’s own blog, so the workflow below is guidance for using Nellie rather than an independent comparison of writing tools. It focuses on four practical criteria: control over the larger arc, consistency between books, a satisfying experience within each volume, and efficient revision. Generated prose still requires close author review.
Start with the series promise#
Before outlining individual books, write one paragraph explaining what readers can expect from the series. This is not promotional copy. It is a creative constraint that helps you decide which ideas belong.
Include:
- Genre and intended audience
- Main source of conflict
- Recurring character or group
- Setting and important rules
- Emotional experience
- What changes from book to book
- What remains familiar
For example, a cozy mystery series might promise a complete village mystery in every volume while gradually revealing why the protagonist left her previous career. An epic fantasy might resolve one regional conflict per book while advancing a war that spans the entire series.
A clear promise prevents a common structural problem: Book 1 feels like an intimate mystery, Book 2 abruptly becomes a military thriller, and Book 3 introduces a new cosmology that contradicts both.
Build a series bible before generating Book 1#
Your series bible is the authoritative record for facts that must survive across installments. Keep it outside any individual manuscript so you can update and reuse it.
A useful series bible has six sections:
- Premise and rules: What is possible in this world, what is impossible, and what consequences follow.
- Character profiles: Appearance, age, background, voice, motives, fears, relationships, skills, secrets, and known history.
- Location profiles: Geography, travel constraints, atmosphere, recurring landmarks, and who controls each place.
- Master timeline: Dates, ages, journeys, deaths, discoveries, injuries, and other irreversible events.
- Arc ledger: Questions raised, answers revealed, promises made to readers, and plots still unresolved.
- Terminology sheet: Spellings, titles, invented vocabulary, organizations, technology, and naming conventions.
Separate fixed facts from flexible plans. A character’s established eye color is fixed once it appears in a published book. A tentative romance in Book 4 remains flexible until you commit to it on the page.
Give every important fact a status such as planned, drafted, or established. This stops an abandoned outline idea from being mistaken for canon.
Map the multi-book arc at three levels#
Plan the series from broad to narrow rather than writing five equally detailed outlines at once.
Level 1: The series arc#
Write the starting state, final state, and major turning points. Identify what the protagonist believes at the beginning and what they must understand by the end.
Level 2: The volume arcs#
Give every book its own goal, opposition, climax, and meaningful resolution. A volume can leave larger questions open, but it should not feel like several hundred pages of setup for the next installment.
Level 3: The chapter outline#
Develop the detailed chapter sequence only when you are preparing to generate that volume. Later books will benefit from discoveries and revisions made while drafting earlier ones.
A compact planning table can include:
| Book | Standalone conflict | Series development | Character change | Ending hook |
|---|---|---|---|---|
| 1 | Immediate problem introduced and resolved | Central mystery discovered | Hero chooses to investigate | Evidence points to a larger threat |
| 2 | New local conflict | Rival faction exposed | Hero learns to trust an ally | Ally’s secret changes the mission |
| 3 | Consequences of that secret | Central mystery reframed | Hero accepts personal responsibility | Final confrontation becomes unavoidable |
This table is an invented structural example, not a prescription. A romance sequence, detective series, or family saga may need a different pattern.
Turn the bible into a focused prompt for each book#
Nellie generates full-length books from a prompt and tracks prior chapters and notes within a book, according to the FAQ. That within-book context can support consistency during one generation, but it does not replace your cross-book records.
Do not paste every note you have collected into every prompt. Include the information that affects the current volume, then summarize the rest.
A practical prompt structure is:
- Book identity: Series title, volume number, genre, audience, and point of view
- Series context: What happened previously and what readers already know
- Canon facts: Relevant character profiles, world rules, terminology, and timeline dates
- Current-book arc: Inciting event, escalating complications, midpoint, climax, and resolution
- Series obligations: Threads to advance, questions not to answer yet, and future developments not to foreshadow
- Style constraints: Tone, tense, pacing, chapter approach, and content boundaries
- Continuity warnings: Facts that are easy to contradict
Invented worked example#
Suppose Book 2 begins six months after Book 1. Your prompt might say:
Mara is now 31. Her left hand was permanently injured during the observatory fire, so she cannot perform tasks requiring a strong two-handed grip. She knows that Tomas forged the expedition permit, but she does not know why. Readers know the northern signal is artificial. No character yet knows who transmitted it. Resolve the missing-cartographer plot in this volume, advance the signal mystery, and do not reveal the transmitter’s identity.
This is more useful than asking for “the next exciting book.” It distinguishes character knowledge from reader knowledge and protects a future reveal.
Reuse profiles without freezing character growth#
Copying the same profile into every prompt can keep surface details stable, but characters should not remain emotionally unchanged.
Create two blocks for each recurring character:
- Permanent or established facts: Family history, physical traits, formative events, enduring speech patterns
- Current state at the start of this book: Beliefs, loyalties, injuries, knowledge, suspicions, and relationships
After completing a volume, update the current-state block. Record only changes that happened in the manuscript, not changes that existed solely in an earlier outline.
It also helps to track knowledge separately. Write entries such as:
- Mara knows the permit was forged.
- Tomas knows who sent the signal.
- The reader suspects Tomas is involved but has no confirmation.
Many apparent plot holes are really knowledge errors, such as a character reacting to information they never received.
Run a continuity edit after every generation#
Nellie can produce a complete draft, but generation is the beginning of the editorial process. Review each book on its own, then compare it with previous installments.
Use separate editing passes instead of trying to catch everything at once:
- Plot pass: Does cause lead to effect? Are setups paid off? Does the climax resolve the volume’s central conflict?
- Character pass: Check appearance, motivation, abilities, voice, relationships, injuries, and knowledge.
- Timeline pass: Verify dates, ages, seasons, travel times, recovery periods, and event order.
- World-rule pass: Confirm that magic, technology, institutions, and geography behave consistently.
- Series-arc pass: Mark which long-term threads advanced, stalled, changed, or closed.
- Reader-knowledge pass: Check that reminders are sufficient without repeatedly explaining previous books.
Search the manuscript for recurring names, places, titles, distinctive objects, and numerical details. Compare every occurrence with the bible. Nellie’s FAQ lists exports including Markdown, HTML, plain text, and JSON alongside reading formats, which can make text-based checking easier, although you should confirm current export availability for your account before choosing a workflow.
Maintain a continuity changelog after the edit. A short entry might read: “Book 2 ends on 18 October; Mara learns the signal originated offshore; Tomas loses his council position; the brass key remains missing.” This becomes the starting context for Book 3.
Keep readers engaged across installments#
Series continuity is not only about preventing errors. It also controls anticipation.
For each volume, decide which threads will be:
- Resolved completely
- Advanced but left open
- Complicated by new information
- Deliberately held back
- Introduced for a later payoff
Limit ending hooks to developments that materially change the next book. A random last-page villain can feel artificial. A trusted ally making a choice that transforms the established conflict gives readers a concrete reason to continue.
Recurring exposition also needs restraint. Give returning readers a concise reminder through action, dialogue, or consequence. Provide enough context for someone who has forgotten a detail, but avoid summarizing the previous book whenever a familiar character appears.
Treat each completed book as the source of truth#
Outlines change during drafting. Once you finish revising an installment, reconcile the bible with the actual manuscript before starting the next one.
Archive three items together:
- The final manuscript
- The updated series bible and timeline
- A short volume summary containing only established events
Then use that summary, the relevant profiles, and the next volume’s outline to create your new Nellie prompt. If you are still developing the opening installment, the workflow in Turn a story idea into a novel provides a more detailed premise-to-draft process.
The essential principle is simple: let Nellie generate each book from a rich, controlled brief, but keep the series canon in an author-maintained system. That combination gives every volume room to develop while preserving the facts, promises, and emotional progression that make a series feel whole.
