From Idea to Book: the Table-of-Contents Method

• Why TOC-first works
• Step 1: the brief
• Step 2: the table of contents
• Step 3: chapter-by-chapter drafting with continuity context
• Step 4: revision passes
• Practical notes

Why TOC-first works

Asking a model to "write a book about X" produces something book-shaped but hollow: repetitive chapters, drifting terminology, no arc. The problem is scale — a book does not fit in one prompt's working attention, so the model plans and drafts and self-edits everything simultaneously, and does each poorly.

The table-of-contents method fixes this by separating planning from drafting. You lock the structure first, then draft one chapter at a time, feeding each session just enough context to stay continuous with the rest. Structural mistakes get fixed at the outline stage, where changing them costs a sentence instead of a rewrite. The same workflow applies to any long document: courses, documentation, reports, long guides.

Step 1: the brief

The brief is a short document answering: what is this book, who is it for, and what changes for the reader by the end. Write it with the model's help, but you make the calls.

I want to write a practical book teaching home cooks to bake
sourdough bread. Interview me to build a one-page brief. Ask about:
audience and their starting skill level, what the reader should be
able to do after finishing, tone, length, what comparable books
get wrong, and what to deliberately leave out. One question at a
time. When done, write the brief.

A usable brief fits on a page and includes: audience, promise to the reader, tone, approximate length (chapter count and words per chapter), and explicit non-goals. The non-goals matter most — they are what keeps chapter 7 from wandering into territory you excluded on purpose. Save the brief; every later prompt starts with it.

Step 2: the table of contents

With the brief locked, generate the skeleton — and make the model give you more than chapter titles, because titles alone hide structural problems.

Here is the brief for my book: [paste brief]

Propose a table of contents: 10-14 chapters. For each chapter give
- a working title
- a 2-3 sentence summary of what it covers
- what the reader can do after it that they couldn't before
- which earlier chapters it depends on

Then critique your own TOC: where might readers get lost, what's
redundant, what's missing given the brief?

Iterate here as long as it takes. Reorder, merge, cut, and re-ask until the dependencies flow and every chapter earns its place. This is the highest-leverage stage of the whole workflow — an hour spent here saves days later. When it is right, have the model produce a clean final TOC document with all four fields per chapter, and treat it as frozen unless drafting reveals a real problem.

Step 3: chapter-by-chapter drafting with continuity context

Draft each chapter in its own conversation. The craft is in the hand-off: each session needs the brief, the TOC, and a summary of what has already been written — not the full text of previous chapters, which would bloat the context, but a compact continuity summary.

You are drafting chapter 5 of a book. Materials:

BRIEF: [paste]

FULL TOC: [paste]

CONTINUITY SUMMARY of chapters 1-4: [paste — key points made,
terms defined, examples introduced, promises made to the reader]

Now write chapter 5 ("Shaping and Scoring") per its TOC entry,
around 3,000 words. Rules:
- Use terminology exactly as defined in the continuity summary.
- You may refer back to earlier chapters; never re-explain them.
- Do not cover anything assigned to later chapters. If chapter 5
  genuinely needs it, insert [FORWARD-REF: topic] and move on.
- End with a 150-word continuity summary of this chapter for use
  when drafting chapter 6.

That closing instruction is what makes the loop run: each chapter emits the summary the next chapter consumes. Append it to your running continuity document, review the draft, request targeted fixes in the same conversation, then open a fresh conversation for the next chapter. The recurring example (in this case, one loaf followed across the book) is worth planting in the continuity summary early — threads like that are what make separately drafted chapters read as one book.

Step 4: revision passes

Revise in separate passes, each with one concern, because "improve this chapter" produces vague general polish while single-purpose passes produce specific fixes.

A consistency pass across the whole book:

Here are the continuity summaries for all 12 chapters, plus the
brief. Check for: terms used inconsistently, promises made to the
reader that no chapter fulfills, [FORWARD-REF] markers I inserted
while drafting, and topics explained twice. Output a numbered fix
list citing chapter numbers. Do not rewrite anything yet.

Then per-chapter passes, one lens at a time — accuracy ("check every factual claim and temperature against the source notes I paste below"), voice ("the brief says warm and unfussy; flag sentences that read as textbook"), and reader-experience ("read as a first-time baker: where would you be confused or need a photo?"). Apply fixes yourself or via targeted prompts; avoid asking for full-chapter rewrites at this stage, which discards prose you have already vetted.

Practical notes

Keep three living files outside any conversation: the brief, the frozen TOC, and the growing continuity summary. They are the memory of the project; conversations are disposable, these files are not. Expect drafting to reveal occasional flaws in the TOC — when that happens, update the TOC document deliberately rather than letting a chapter silently diverge from it. And expect the model's role to shift across the workflow: interviewer at the brief stage, architect at the TOC stage, drafter in the middle, and checklist-driven editor at the end. The method's whole trick is never asking it to be all four at once.