How to Write a Book with AI Agents, Step by Step

You write a book with AI agents in six phases, run in order: vision, bible, draft, review, revise, publish. You answer the questions about what the book is for and who reads it, writer agents take chapters on branches, an orchestrator reads every chapter before it merges, and the last phase produces the print-ready PDF, the cover, the KDP package, and the Kindle file. You decide what the book says. Your agent does the 100 hours.

What do you need before you start?

Claude Code, plus the free tools the pack lists: Calibre, pandoc, and a LaTeX engine. The installer tells your agent what is missing and how to get it, so you are not hunting down dependencies on your own. You open a terminal once and paste one line. From there you talk to your agent in plain English.

Two setup details that matter more than they sound. First, let the agent run without stopping to ask you about every file write: in Claude Code press Shift+Tab until the status line reads auto-accept edits, or start it with claude --dangerously-skip-permissions for the full hands-off run. Your agent can tell you which one to use.

Second, every draft lives in git. Git is Time Machine for a project: every chapter, every revision, rolled back with one command if you ever want an earlier version. Your agent sets it up. You do not have to touch it. That is what makes the rest of this safe to run fast, because nothing you produce can be lost by a bad revision pass.

Phase one: how do you give the agent the vision?

Tell your agent to ask you the vision questions one at a time. That instruction is in the paste block on the Write Books sales page for a reason. Handed a wall of text, an agent fills the gaps with plausible nothing. Asked one question at a time, it gets the answer you would actually give out loud.

The questions: what the book is for, who reads it, what happens after they finish it, fiction or nonfiction, and the voice. Answer them like you are talking, not like you are writing jacket copy. This is the phase that is genuinely yours, and it is the only one that stays yours all the way through.

Phase two: what goes in the bible?

Your agent builds the bible from your answers: voice, characters or frameworks, and the chapter-by-chapter outline. Read it before you let anything else run. It is the shortest document in the whole build and it is the one that decides the book.

The bible is also the pass/fail standard the orchestrator uses in phase four. Anything that is not in the bible is not enforced. So if there is a phrase you never want to see, a story that has to land in chapter three, or a framework that carries the middle of the book, it goes in the bible now, not in a note to yourself later.

Phase three: how does the drafting actually work?

Writer agents take chapters on branches, each one carrying the bible and the prior chapters for continuity. /writebooks plans and writes the manuscript with a team of writer agents and one orchestrator that reviews every chapter before it merges.

Fiction and nonfiction run the same phases with different bibles. Nonfiction runs one writer per book for voice consistency. Fiction runs a fleet: the James trilogy came out of eight writer agents working in sequential batches, 78 chapters, three novels in one voice.

Branches are the part people skip past, and they are the point. A chapter on a branch is not in your book yet. It is a candidate. Nothing becomes the manuscript until somebody reads it.

Phase four: what does review actually mean?

The orchestrator reads every chapter, sends back what fails, and merges what passes. Six phases, one orchestrator, zero unsupervised merges. That last part is the whole quality mechanism: nothing gets into the manuscript that has not been read against the bible.

A high rejection rate early is not a problem with the pipeline. The rejection rate is the quality signal.

That lesson came out of the DaD Papers build and it is in the case study inside the pack, along with one writer per nonfiction book and write the bridge last. If chapters are sailing through on the first pass, your bible is too loose to fail anything. Tighten it and re-run.

Phase five: how do you revise without saying make it better?

The revision phase is a hill-climb pass on named prose patterns, not vague make it better. Name the patterns. On the fiction trilogy, one revision pass fixed exactly five named patterns, and that specificity is the difference between AI wrote a book and a book.

Here is how you find the patterns worth naming, and it is the best two hours you will spend on your own book. Put the draft on your Kindle. Read it with a voice recorder going, and say your notes out loud as they come. Do not stop to type. Transcribe the voice note, hand it to your agent, and it keeps revising until it sounds like you.

Reading on the Kindle instead of in the editor changes what you notice. You stop seeing a file you could fix and start seeing a book somebody handed you. That is the stance you want: you read the draft the way an editor reads it, not the way an author sweats it.

Phase six: which commands publish the book?

Phase six is where the pipeline stops being about words and starts being about files. Each command is one job:

The Amazon upload itself is a manual step. Your agent walks you through it. Upload to ACX for the audiobook is manual too, and the command walks you through that one as well.

So what is your job in all of this?

Two things, and they do not change no matter how good the agents get.

1. You decide what the book says. The stories, the frameworks, the argument, who it is for, what you want them to do when they close it. No agent can source that from anywhere but you.
2. You read the draft like an editor. Not like an author. An editor asks whether chapter nine earns its place. An author rewrites chapter nine nine times and never gets to chapter ten.

Everything between those two jobs is the pipeline: the chapter drafts, the continuity, the interior typesetting, the cover wrap math, the metadata Amazon accepts, the Kindle file. That is the trade the Write Books pack makes. The book stops being a project and becomes an output.

Common questions

What do I need installed to write a book with AI agents?

Claude Code, plus the free tools the pack lists: Calibre, pandoc, and a LaTeX engine. The installer tells your agent what is missing and how to get it. You open a terminal once and paste one line, and after that you talk to your agent in plain English.

How long does it take to write a book this way?

The pipeline is built to run manuscript to Kindle in one session. Days, not years. The slow part is no longer the writing, it is you deciding what the book says and reading the draft the way an editor reads it.

How do I keep the book from sounding like AI wrote it?

Three mechanisms stack. The bible carries your voice, your stories, and your frameworks. The orchestrator rejects chapters that fail the bible instead of merging them. Then the revision pass hill-climbs on named prose patterns rather than a vague instruction to make it better. On the fiction trilogy that pass fixed exactly five named patterns.

What happens if a chapter comes out wrong?

Every draft lives in git, which is Time Machine for a project: every chapter, every revision, rolled back with one command if you ever want an earlier version. Your agent sets it up and you do not have to touch it.