A fantasy novel becomes easier to draft when its wonders create problems as reliably as they solve them. Before generating prose, define the story promise, time setting, magic rules, factions, and core facts of the invented world. Then turn those constraints into scenes.
This preparation does not require a vast encyclopedia. It requires a small, authoritative record that answers the questions most likely to affect the plot. Nellie can generate a complete, full-length book from a prompt, according to its current FAQ, but a clear brief gives the resulting draft firmer boundaries. You will still need to review the manuscript for contradictions, repetition, unsupported factual claims, and accidental changes to your lore.
Fix the premise and time setting first#
Start with the story, not the map. Write one sentence containing four elements:
- A protagonist with an immediate goal
- An unusual feature of the world
- An opposing force
- A consequence of failure
“An apprentice studies forbidden magic” is an atmosphere, not yet a novel premise. A more useful version is: “An apprentice who can hear broken oaths must expose the treaty keeping her city alive before its enforcers erase her family’s names.”
Next, establish when the story happens relative to the events that shaped the world. An invented calendar is optional. Sequence is not.
Record five anchors:
- The old event people still argue about
- The recent event that changed daily life
- The incident that begins the novel
- The deadline driving the plot
- The provisional ending state
For example, an empire may have collapsed 80 years ago, but the more relevant fact could be that its sealed roads reopened six months before chapter one. That recent change can affect trade, migration, military plans, and what characters believe is possible.
If your novel uses multiple eras, label each scene with its date or relative position. “Three nights before the coronation” is more useful during planning than an elaborate calendar whose months never affect the action.
Give magic powers, prohibitions, costs, and counters#
A usable magic system answers more than “What can a mage do?” It establishes why magic cannot end every conflict immediately.
Define each major form of magic with six questions:
- Access: Who can use it, and how do they gain that ability?
- Effect: What can it change, reveal, create, or destroy?
- Prohibition: What can it never do?
- Cost: What does each use consume, risk, or damage?
- Limit: What conditions restrict range, duration, scale, or frequency?
- Counter: How can another person resist, interrupt, detect, or exploit it?
Make costs consequential rather than decorative. If spellcasting causes mild fatigue but the caster recovers whenever convenient, the cost will not shape decisions. A stronger cost forces a tradeoff. Perhaps healing transfers the injury to the healer, truth magic reveals one of the questioner’s secrets, or teleportation works only between gates controlled by rival factions.
Counters matter just as much. Without them, opponents survive only because the plot temporarily makes the protagonist forget what magic can do. A counter might be a material, ritual, environmental condition, competing spell, social prohibition, or tactical response.
Run three stress tests before drafting:
- The locked-room test: Can this power bypass ordinary barriers? If so, what replaces those barriers as meaningful obstacles?
- The murder test: Why can its users not eliminate every enemy from a distance?
- The economy test: If the power creates food, heals injuries, predicts weather, or moves goods, how has society changed around it?
You do not need to explain every implication to readers. You do need to know enough to prevent an easy solution from appearing only in the climax.
Build factions around incompatible goals#
A faction is more than a name, color, and uniform. It is a group pursuing a goal through recognizable methods.
For each important faction, record:
- Public goal
- Actual priority
- Source of power
- Method it considers acceptable
- Action it refuses to take
- Internal disagreement
- Desired use or suppression of magic
- What it needs from the protagonist
Opposition is strongest when factions want outcomes that cannot all coexist. Suppose the river guild wants unrestricted gate magic to restore trade. The border monasteries want every gate sealed because travel weakens a prison beneath the mountains. The crown wants controlled access so it can tax movement and deploy soldiers. None needs to be wholly right or evil.
Give factions internal pressure too. A guild can contain merchants who want stability and smugglers who profit from disruption. This creates allies, betrayals, and difficult negotiations without requiring a new villain whenever the plot slows.
Finally, connect faction strategy to resources. If a faction has spies but no army, its scenes should emphasize information, blackmail, and infiltration. If it controls the only counter to magic, that advantage should affect diplomacy as well as combat.
Invented worked example: from vague magic to a scene outline#
The following example was invented for this article. It is not a generated result, published novel, or customer story.
Vague premise: A young mapmaker uses memory magic to stop a war between rival kingdoms.
This leaves several easy escapes. What can memory magic alter? Why not erase both rulers’ hostility? How can anyone resist it?
Revised premise: Mapmaker Sera can transfer one witnessed memory into a hand-drawn map, but doing so permanently removes the memory from its original owner. When two city-states mobilize over a disputed massacre, she must prove that both governments altered the official account before the last neutral bridge closes at dawn.
Rules:
- Sera can copy only a memory she personally sees during skin contact.
- The map records places and actions, not private thoughts.
- The original owner loses the transferred memory.
- Each map can hold one memory and burns when read.
- Saltwater dissolves the stored memory without revealing it.
- Trained archivists can detect a transfer from gaps in sensory recall.
Faction conflict:
- The Bridge Council wants peace but will suppress evidence that could trigger riots.
- The Ash Regiment wants the massacre blamed on its enemy so mobilization continues.
- The Archivists want all memory maps confiscated because the practice destroys testimony.
Scene outline:
-
Objective: Sera touches a surviving soldier to recover his memory of the massacre.
Obstacle: He knows the transfer will leave him unable to testify.
Turn: He agrees only if Sera promises to show his daughter first. -
Objective: Sera carries the map across the neutral bridge.
Obstacle: Ash Regiment agents flood the checkpoint with saltwater.
Turn: She saves the map but reveals that she possesses forbidden memory magic. -
Objective: Sera presents the evidence to the Bridge Council.
Obstacle: Reading it will burn the only copy, while withholding it allows the war deadline to pass.
Turn: She discovers the map shows soldiers from both states obeying a third faction.
The rules now produce the scenes. The cost creates an ethical conflict, the counter creates physical danger, and the one-use limit makes the hearing consequential.
Keep a worldbuilding ledger that separates lore from evidence#
Invented names drift easily. A character becomes Liora in one chapter and Liara in another. Eastmere turns into Eastmarsh. A temple that prohibited iron suddenly has iron gates.
Maintain one source-of-truth ledger outside the manuscript. Copy this table into a document or spreadsheet:
| Entry | Type | Canonical spelling | Fixed fact or rule | Status | First appearance | Story consequence | Real-world source needed? |
|---|---|---|---|---|---|---|---|
| Sera Venn | Character | Sera Venn | Cannot recover a transferred memory | Fixed | Ch. 1 | She cannot undo her central sacrifice | No |
| Vey Bridge | Place | Vey Bridge | Neutral until dawn on treaty day | Fixed | Ch. 2 | Creates the deadline | No |
| Memory map | Magic | memory map | Burns after one reading | Fixed | Ch. 1 | Evidence cannot be reused | No |
| Funeral custom | Culture | Lantern Wake | Inspired by real mourning traditions | Draft | Ch. 4 | Shapes alliance scene | Yes |
Use status labels such as idea, planned, drafted, and established. A possibility in your notes is not canon merely because you wrote it down.
Also keep invented lore separate from real myth, religion, language, and history. If you borrow the name of a deity, ritual, historical people, sacred object, or traditional story, record its source and verify the context. Decide whether you are adapting it openly or creating something new.
Generated passages can combine plausible and invented details in a confident voice. Treat factual claims as unverified until you confirm them against suitable sources. Nellie’s manuscript editing guide recommends recording claims in an evidence ledger and checking dates, quotations, historical details, scientific explanations, and other factual material before distribution.
Turn the ledger into a generation brief#
Condense the material that affects this book into a practical prompt:
- Premise, protagonist, goal, stakes, and ending direction
- Time setting and important deadlines
- Magic rules, costs, prohibitions, and counters
- Factions, resources, goals, and internal disputes
- Canonical names for major characters and places
- Cultural rules that affect scenes
- Facts characters know at the opening
- Revelations that must remain hidden until specified chapters
- Point of view, tense, tone, and content boundaries
- Scene or chapter outline
Nellie’s FAQ says its large-context system tracks prior chapters and notes within a book. That documented feature can support long-form development, but it does not establish flawless continuity. Keep your own ledger and compare it with the completed draft. For the broader path from premise to revision, see the first-book workflow, which recommends maintaining a continuity sheet for names, physical details, locations, world rules, and the story timeline.
Writers deciding between complete-book generation and more incremental assistance can also consult the long-form fiction tools comparison. Because that comparison appears on Nellie’s own blog, it is not an independent product review. It evaluates documented outline control, continuity support, drafting granularity, and revision workflow rather than claiming that one tool produces objectively better fantasy prose. Product capabilities can change, and documented context or memory features do not prove error-free continuity.
Fantasy consistency checklist#
Before generation:
- [ ] The premise identifies a protagonist, goal, opposition, and consequence.
- [ ] The story’s era and main deadline are fixed.
- [ ] Every plot-critical power has a prohibition, cost, limit, and counter.
- [ ] Magic cannot provide an unexplained last-minute solution.
- [ ] Factions pursue incompatible goals through distinct methods.
- [ ] Canonical spellings are recorded for names, titles, and places.
- [ ] Invented lore is clearly separated from real references.
- [ ] Character knowledge is distinguished from reader knowledge.
After generation:
- [ ] Every use of magic follows the established rules.
- [ ] Costs still matter after major spells.
- [ ] Travel, injuries, seasons, and deadlines remain plausible.
- [ ] Faction behavior matches its goals and resources.
- [ ] Characters do not know facts they have not learned.
- [ ] Names and titles match the ledger.
- [ ] Real myths, historical claims, and cultural references are verified.
- [ ] Revisions have not left obsolete lore elsewhere in the manuscript.
A full editorial pass should move from structure to continuity and only then to sentences. The AI manuscript editing checklist provides a reusable sequence and explains why structural problems should be addressed before line-level polishing.
Your next step is concrete: enter the premise, magic rules, and faction list in Nellie before generating. Include the names-and-places ledger and at least a provisional ending. The goal is not to remove surprise from the draft. It is to make every surprise obey the world that produced it.



