Writing with AI
AI Book Writing Workflow: 8 Steps From Brief to Publish Files
By the Inkora team · Oct 29, 2026 · 10 min read
A reliable AI book writing workflow has eight stages: write a clear brief, turn it into a book bible, approve a chapter-by-chapter outline, generate chapters one at a time, check continuity, edit the draft yourself, clean out the "AI tells," and export publish-ready files. The AI does the most work in the middle. The decisions at the start and the editing at the end are yours, and they determine whether the book is any good.
This guide walks through each stage, explains what can go wrong, and ends with a checklist you can reuse for every book.
What an AI book writing workflow looks like from start to finish
Think of it as a funnel. Each stage narrows the possibilities so the next one has less room to drift. A vague prompt produces a vague book. A detailed plan produces a draft you can actually edit.
| Stage | What you produce | Your main job |
|---|---|---|
| 1. Brief | One page describing the book | Make the core decisions |
| 2. Book bible | Premise, characters or concepts, style guide | Correct and expand it |
| 3. Outline | Chapter-by-chapter plan | Approve it before any drafting |
| 4. Chapter generation | Full draft, chapter by chapter | Review each chapter as it lands |
| 5. Continuity checks | List of contradictions and fixes | Catch errors across chapters |
| 6. Human edit | Revised manuscript | Rewrite, cut, verify facts |
| 7. AI-tell cleanup | Prose that reads as yours | Remove patterns readers notice |
| 8. Publish files | Interior, cover, ebook, metadata | Format for each store |
If you are new to the idea, how to write a book with AI covers the basics. This article focuses on the process.
What goes in the brief
The brief is a short document that answers the questions an editor would ask before agreeing to a project. Skip it and the AI will fill the gaps with the most generic choices available.
Cover these points:
- Idea: one or two sentences on what the book is about.
- Book type and genre: cozy mystery, practical guide to home composting, picture book for ages 4–6, and so on.
- Audience: who reads it and what they already know.
- Tone: dry and funny, warm and reassuring, tense and spare.
- Point of view: first person, close third, or "you" for non-fiction.
- Language: the language the book is written in.
- Target length: a word count range, not a page count.
- What it is not: genres, clichés or topics you want kept out.
The last point helps more than people expect. "No love triangle" or "don't assume the reader owns a stand mixer" saves you from rewriting whole chapters later.
If you are unsure about length, how many words in a novel gives genre-by-genre guidance.
What a book bible is, and why to build it before the outline
A book bible is the reference document that keeps a long book consistent. For fiction it holds the premise, character profiles (names, ages, appearance, motives, how each one speaks), settings, timeline and rules of the world. For non-fiction it holds the central argument, key concepts with fixed definitions, the reader's starting point and the promised outcome.
It also includes a style guide. This covers the narrator's voice, sentence length, tense, spelling conventions (US or UK), how dialogue is punctuated, and words to avoid.
Build the bible before the outline because the outline depends on it. A character's backstory changes which scenes make sense. A concept's definition changes which chapters come first. For a fuller explanation, see what is a book bible.
In Inkora, the brief is turned into a draft book bible that you edit before anything is written. Treat that draft as a proposal, not a finished document. Rename characters, sharpen the premise and rewrite the style guide in your own words.
How to approve an outline before generating chapters
The outline is the cheapest place to fix a book. Changing one line in an outline takes seconds. Changing a chapter that was built on a bad line takes an afternoon.
Read the outline as a whole and check the following:
- Every chapter should have a job. In fiction, something should change. In non-fiction, the reader should learn or be able to do something new.
- The order should hold up. Look for setups that come after their payoffs, or concepts used before they are explained.
- The pacing should be even. Watch for three quiet chapters in a row, or a climax squeezed into one paragraph of summary.
- The ending should deliver what the premise promised.
- Chapter lengths should be roughly consistent with your target word count.
Write a few sentences of detail under each chapter heading: key events, the point of view character, the takeaway. The more specific each entry, the less the AI improvises. How to outline a novel covers structure options if your plan feels shapeless.
Do not move on until you would be happy reading a book that followed this outline exactly.
How to generate chapters with AI
Generate one chapter at a time, in order, and read each one before moving on. Generating the whole book in one go and reading it at the end is how small errors turn into structural ones.
Feed each chapter the context it needs: the book bible, the outline entry for that chapter, and a summary of what has already happened. Good tools do this automatically. Inkora, for example, writes each chapter with running continuity notes, a locked narrator voice and a fact ledger that records established details so later chapters stay consistent with earlier ones.
When a chapter comes back, check three things quickly:
- That it followed the outline entry.
- That the voice matches the style guide.
- Whether it invented anything new that matters later, such as a name, a rule or a statistic.
If a chapter misses badly, regenerate it rather than patching it line by line. If it is mostly right, keep it and note the fixes for the editing stage. Add any newly invented details you want to keep to your book bible so they stay fixed.
How to check continuity across chapters
Even with good context, long drafts drift. Continuity checks catch the contradictions a single-chapter read misses.
Common continuity errors in AI drafts:
- A character's eye colour, age or job changes.
- Characters know things they have not learned yet.
- The timeline breaks: a week passes in one chapter and only a day in the next.
- A non-fiction term is defined one way early and used differently later.
- The same anecdote, example or metaphor appears twice.
- Minor characters vanish without explanation.
A practical method is to keep a running sheet as you read: one column for each character or key concept, with every fact recorded and the chapter it appears in. Contradictions show up quickly when they sit next to each other.
Read the full draft in one or two sittings if you can. Repetition and pacing problems are much easier to spot at speed than across several weeks.
How much human editing an AI draft needs
Plan for real editing, not a light proofread. The AI produces a draft. You produce the book.
Work in passes, from big to small:
- Structural pass: cut chapters that repeat, merge thin ones, reorder where the logic breaks.
- Scene or section pass: make sure each scene has tension or each section has a clear point. Trim padding.
- Line pass: rewrite flat sentences, vary rhythm, sharpen dialogue so each character sounds different.
- Fact pass: verify every claim, name, date, figure, quote, recipe quantity and instruction. AI tools can state false things confidently, and you are responsible for what you publish.
- Proofread: typos, formatting, consistent spelling.
Add what only you can add: personal experience, specific detail, opinions, jokes, and the scenes you actually care about. This is where an AI-assisted book becomes your book. How to edit your own book goes deeper on self-editing technique.
How to remove AI tells from the prose
Readers who have seen a lot of AI text recognise certain patterns. None of them is wrong on its own. In bulk they make a book feel machine-made.
Look for:
- Stock phrases: inflated, ornamental vocabulary that turns up in AI text far more often than in human writing, plus phrases such as "a sense of" or "couldn't help but."
- Lists of three everywhere: "brave, kind and determined" in every other paragraph.
- Neat endings: every chapter closing on a reflective summary or a hopeful line.
- Named emotions: "She felt a wave of sadness" instead of showing what she does.
- Same-shaped sentences: long sentence, comma, participle phrase, repeated for pages.
- Over-explaining: dialogue followed by narration that explains what the dialogue meant.
- Hedging in non-fiction: "it's worth considering that," "in many ways," "can be a powerful tool."
- Identical chapter openings: weather, a character waking up, or a sweeping general statement.
Search the manuscript for your worst offenders and fix each instance by hand. Cutting a final reflective paragraph often improves a chapter instantly. Reading aloud is the fastest way to hear repetitive rhythm.
The files you need to publish
Once the text is final, you need a set of files, and each store has its own requirements.
- Print interior PDF at your chosen trim size (6x9 is common for novels and non-fiction).
- Full-wrap paperback cover PDF with back, spine and front. Spine width depends on page count and paper, so finalise the interior first. KDP's published terms require 0.125" bleed on every edge.
- Ebook cover image. KDP recommends 1600 × 2560 px JPEG or TIFF in RGB. Apple Books asks for at least 1400 px on the shortest side.
- EPUB for ebook stores.
- Metadata: title, subtitle, description, keywords, categories, author bio.
ISBN rules differ. According to each store's published terms, KDP ebooks don't need one (Amazon assigns an ASIN), KDP paperbacks need one (KDP offers a free one that only works on KDP), and IngramSpark requires your own ISBN for each format. Confirm the current rules in each store's dashboard before you upload.
Inkora exports a print-ready interior PDF in eight trim sizes, a full-wrap cover PDF with spine width calculated from the page count, a 1600 × 2560 Kindle cover JPG, EPUB 3, DOCX and a publishing kit with description, keywords and BISAC categories. You still upload to each store from your own account. Store-by-store steps are on the publishing guides page, and you can estimate length beforehand with the book page count calculator.
Before you publish, read is it legal to sell AI-written books. Some stores, including KDP, ask about AI-generated content during setup, so check the current wording when you get there.
The AI book writing workflow checklist
Planning
- Brief covers idea, type, genre, audience, tone, POV, language, length and exclusions
- Book bible reviewed and rewritten in your words
- Style guide includes voice, tense, spelling and banned words
- Outline approved, with a clear job for every chapter
Drafting
- Chapters generated in order, one at a time
- Each chapter checked against its outline entry and the style guide
- New details added to the book bible
- Failed chapters regenerated, not patched
Revision
- Full read-through for continuity, with a running fact sheet
- Structural, scene and line edits done
- Every fact, figure, quote and instruction verified
- AI tells searched for and fixed
- Final proofread
Publishing
- Trim size chosen and interior PDF exported
- Cover built after final page count
- Ebook cover and EPUB exported
- Metadata, description and categories written
- ISBN plan decided per store
- Proof copy ordered and checked
- Royalty rates and AI disclosure questions confirmed in each store's dashboard
Common problems and fixes
The draft sounds generic. The brief or style guide was too thin. Add specific voice instructions and a sample paragraph in the tone you want, then regenerate the weakest chapters.
The story drifted from the outline halfway through. Find the first chapter where it went off course and regenerate from there with a more detailed outline entry. Fixing later chapters without fixing the cause rarely works.
Characters all sound the same. Add speech notes to each character in the book bible, such as vocabulary, sentence length and verbal habits. Then do a dialogue-only edit pass.
Chapters repeat the same points. This is common in non-fiction. Merge overlapping chapters, give each one a single job in the outline, and cut the repeated examples.
You found a factual error after publishing. Correct the manuscript, re-export, and upload the revised files in each store's dashboard. Most stores let you update content on books that are already live.
The book is too short or too long. Expand or condense at outline level first. Adding filler to finished chapters shows. Adding a planned subplot or section does not.
You feel no ownership of the result. Spend more time in stages 2, 3 and 6. The more of your judgment goes into the plan and the edit, the more the book reflects you.
The workflow works because it puts your decisions where they matter most: before drafting and after it. Let the AI handle volume in the middle, and give the brief, the outline and the edit your full attention. Run through the checklist each time, and every book after the first gets faster.
Frequently asked questions
How long does an AI-assisted book take from brief to publish?+
It depends mostly on how long you spend planning and editing, since generation itself is the fast part. Most of your time will go into the outline, the human edit and formatting checks, so budget for those rather than the drafting.
Can I use different AI tools for different stages?+
Yes, but you must carry the book bible and outline between them yourself, or continuity suffers. A single tool that keeps the bible, outline and chapters together reduces copy-paste errors.
Does this workflow work for non-fiction as well as fiction?+
Yes. The stages are the same, but the book bible holds concepts and definitions instead of characters. The fact-checking pass becomes far more demanding because readers act on what you tell them.
Should I tell readers my book was written with AI assistance?+
Some stores ask about AI-generated content during setup, so answer those questions accurately. Whether to mention it in the book or description is your choice, but being honest avoids complaints and reviews that feel misled.
Can I write a book with AI in a language I don't read fluently?+
You can generate it, but you can't properly edit or fact-check a language you don't read well. Hire a fluent editor or proofreader before publishing in that language.
Should I order a printed proof even if the PDF looks fine?+
Yes. Margins, spine text, cover colour and font size often look different on paper than on screen, and a proof copy catches these before readers do.
Turn your idea into a finished book
Inkora plans, writes and formats your book, designs the cover and exports print-ready PDF, EPUB and DOCX for every store.
Start writing free