To write a novel with AI chapter by chapter, work in a loop: plan one chapter, supply relevant context, draft manageable scenes, review the prose, and update your approved notes. Repeat that loop instead of asking for an entire book at once. You remain responsible for the story's choices, voice, and final text.
1. Decide what changes in the chapter
A chapter needs more than a location and a word target. Describe its starting state, pressure, decision, and ending state. In an invented example, Mara enters the tower believing Ivo knows the route. She discovers a missing part of the map, chooses to continue, and leaves with less certainty but a clearer personal stake.
That state change gives the assistant something to develop. “Write an exciting tower chapter” leaves too many important choices unspecified.
2. Prepare only the relevant context
Supply the viewpoint, tense, chapter goal, accepted summary of the preceding scene, and selected bible entries. Include the current location of important objects and the limits of the viewpoint character's knowledge.
Use the AI story bible packet to separate fixed facts from open ideas. State whether the assistant may invent minor characters or new world rules. Do not rely on a long chat history as your only record of canon.
3. Outline scenes before requesting prose
Ask for a small scene list. Each scene should have a goal, obstacle, turn, and consequence. Inspect whether the scenes actually produce the chapter's intended change. Cut a scene that merely repeats information unless the repetition changes its meaning.
Once the outline works, draft one scene. Smaller requests make it easier to catch a wrong assumption before it spreads through an entire chapter. There is no universal ideal word count: choose a scope you can read and revise attentively.
4. Review in separate passes
First review story logic: cause and effect, character choices, and what the scene changes. Next review continuity against your notes. Finally revise voice, rhythm, repetition, and detail. Combining all three into “make this better” can produce polished sentences around a broken scene.
Keep a copy of the original draft when experimenting with revisions. If the assistant changes the plot while improving the prose, compare the versions and restore the choices you intended to keep.
5. Update the accepted state
After accepting the chapter, write a concise summary and update your continuity ledger. Record new information, injuries, possessions, relationship changes, and unresolved promises. Require evidence for updates proposed by an assistant.
The accepted version becomes the next chapter's starting context. Rejected alternatives should not remain mixed into that packet.
6. Review across several chapters
Scene-level editing does not catch every long-range issue. At the end of a sequence, read the chapters together. Look for repeated emotional beats, forgotten consequences, sudden changes in pace, and promises that disappear without resolution.
If chapter seven reveals a problem in chapter three, revise the relevant sequence before producing more prose that depends on it. The useful unit of progress is an accepted, coherent passage, not the number of generated words.
Start with one complete loop using the chapter prompt library. Ficlora currently provides these guides and a local story-concept workbench; it does not yet generate or store full novels for you.
