I Shipped a 370-Page Book in 8 Weeks Using 5 Claude Agents. Here's the Pipeline.

The full Appendix B teardown from my book. The five specialist agents that handled drafting, diagramming, copy-editing, typesetting, and KDP submission — the handoff contracts between them, and the unexpected ways the pipeline broke.

The meta-bet behind the book

I wrote and shipped How to Claude — The Playbook for a One-Person Business in eight weeks. 370 pages. Three Amazon formats (Kindle, paperback, hardcover). 28 chapters. 65 diagrams and illustrations. Four appendices. Solo.

The meta-bet of the project was that the book had to be produced using the same methodology it teaches. If the methodology really lets a solo operator run a small specialist team, it should let a solo operator run a small specialist team to produce a book about the methodology. Anything else would be hypocritical, and the early readers would catch it immediately.

The pipeline I built ran five Claude-driven roles plus me as orchestrator. I wrote every word of prose myself, but the entire production wrap (research support, diagramming, copy editing, typesetting, KDP submission) was handled by specialized Claude agents with their own Skills, CLAUDE.md files, and handoff contracts.

This is the Appendix B teardown — the full production pipeline that shipped the book — pulled from the book itself. It is the closing chapter of the campaign of articles I've been publishing about the book, and the one I tell readers to read if they want to see the methodology in its most condensed and verifiable form.

The five agents

Each agent was a separate Claude session (or, in two cases, multiple sessions running in parallel for the same role). Each agent had:

1. A CLAUDE.md defining its scope, conventions, and what was out of scope
2. A Skill file in ~/.claude/skills/ defining its workflow
3. A handoff contract — the exact format of the artifact it received and the artifact it produced
4. Access to a shared /Users/andygarcia/Documents/how-to-claude/ repo with the book source

The five roles:

Agent 1: Drafter

Took my outlines (one per chapter, roughly 200 words each, hand-written by me) and produced rough chapter prose in my voice.

Skill: how-to-claude-drafter. Loaded with a voice rubric distilled from 30 of my Medium articles, plus 8 "good chapter" examples written by hand for tone calibration.

Handoff in: My one-paragraph outline + a brief on the chapter's role in the book's overall arc.

Handoff out: A 2,500-4,000 word Markdown chapter draft in my voice, with placeholders for diagrams and examples.

Time per chapter: 40-60 minutes of Drafter time, 20-30 minutes of my review time.

The Drafter was where 60% of the book's first-draft prose came from. I'd then heavily revise it, but the cold-start cost of "stare at a blank page" was eliminated. The Drafter's voice was good enough that 30-40% of its output survived to final with only light edits.

Agent 2: Diagrammer

Took prose explanations from the Drafter output and proposed Mermaid flowcharts, sequence diagrams, or commissioned illustrations.

Skill: book-diagram-producer. Loaded with the book's visual style guide (cream + navy palette, hand-drawn sketch aesthetic for conceptual diagrams, Mermaid syntax for technical flows) and 12 example diagrams from the first three chapters.

Handoff in: A chapter draft with [DIAGRAM: description] placeholders marked by the Drafter or by me.

Handoff out: A Mermaid source file per technical diagram, or a structured commission brief for the illustrator on conceptual diagrams (sent to a human illustrator who produced 9 custom pieces).

Time per chapter: 15-25 minutes of Diagrammer time, plus 1-3 days for illustrator turnaround on custom pieces.

The Diagrammer's most valuable role was as a first-pass on diagram-vs-illustration decisions. Most placeholders the Drafter proposed could be solved with a Mermaid diagram; the Diagrammer correctly identified which ones genuinely needed a custom illustration. That decision saved several hundred dollars in illustration costs by routing only the right placeholders to the human illustrator.

Agent 3: Copy editor

Caught every teh, every dangling reference, every passage that drifted out of the book's voice, every place where the same word was used twice in adjacent sentences, every sentence that started with "But."

Skill: book-copy-editor. Loaded with the same voice rubric the Drafter used, plus a list of 40 "violations" — patterns the previous chapters had taught me to flag. The Copy Editor was the role with the most-updated Skill in the project; it absorbed a new note roughly every two chapters.

Handoff in: A chapter that had been through me (revised against the Drafter's first draft).

Handoff out: The chapter with copy-edit suggestions in tracked-change comments, plus a separate "voice drift" report listing any passages that had drifted from the rubric.

Time per chapter: 20-30 minutes of Copy Editor time, 15-20 minutes of my review.

This role caught the kind of mistakes that human editors catch — but it caught them at 6 AM, at 11 PM, on a Sunday, on Christmas Eve. Availability was the value-add. The quality was 80% as good as a professional human copy edit. Combined with my own final read, the quality was equivalent.

Agent 4: Typesetter

Wrestled with LaTeX, Pandoc, and a Lua filter I had to write specifically to stop code blocks from overflowing the 6×9 paperback trim size.

Skill: book-typesetter. Loaded with the LaTeX template, the Pandoc config, the Lua filter, and a list of 22 typesetting gotchas the previous chapters had taught us (orphan lines, widow lines, page-break-after-heading bugs, footnote overflow, etc.).

Handoff in: The final-edited Markdown chapter.

Handoff out: A PDF chapter rendering, with any typesetting issues called out separately for me to decide on (re-flow vs accept).

Time per chapter: 30-45 minutes of Typesetter time, 15-25 minutes of my review on issue triage.

The Typesetter was the most boring of the five and the most reliable. By chapter 10 the Skill had absorbed enough of the project's specific typesetting quirks that the agent could ship a chapter PDF with zero issues 60% of the time. The other 40%, the issues it surfaced were specific and actionable.

Agent 5: KDP submitter

Handled the metadata, the categories, the hardcover case laminate turn-in calculations, and the excruciating dance of getting Kindle Direct Publishing to accept three formats without rejection.

Skill: kdp-submitter. Loaded with KDP's spec docs (cached locally because Amazon's docs change without warning), my account credentials in a secure store, and a checklist of 30+ steps to clear before submission per format.

Handoff in: A final PDF + Kindle file + hardcover wrap PDF, plus a metadata file with title, subtitle, description, keywords, categories, and pricing per region.

Handoff out: A submission status report per format, with any KDP errors translated into "here's what you need to fix" plain English.

Time per format: 45-75 minutes of KDP Submitter time (including waiting for KDP's preview generation), with significant idle waits.

This role was the most underrated. KDP's submission flow is notoriously fiddly — wrong margins on the hardcover wrap, wrong line spacing on the Kindle file, wrong keyword choices that violate Amazon's terms — and each rejection costs you a day. The KDP Submitter caught 90% of the rejectable issues before they hit Amazon's review, saving roughly a week of iteration time.

The orchestration

Me, sitting in Claude Code in the root of the book repo, was the orchestrator. The pattern for any given chapter was:

1. I'd update the chapter's outline file with revisions from my notes.
2. I'd dispatch the Drafter to produce the rough chapter from the outline.
3. I'd revise the rough chapter myself — usually 60-90 minutes per chapter.
4. I'd dispatch the Diagrammer on any diagram placeholders.
5. I'd dispatch the Copy Editor on the post-revision draft.
6. I'd accept/reject the Copy Editor's suggestions.
7. I'd dispatch the Typesetter to produce the chapter PDF.
8. I'd review the chapter PDF and accept or fix any typesetting issues.
9. When all 28 chapters were done, I'd dispatch the KDP Submitter on the three formats.

The dispatch pattern is the part most people miss. I did not run all five agents sequentially per chapter — I'd dispatch the Drafter on chapter 8 while I was revising chapter 7, while the Copy Editor was running on chapter 6. At peak, I had four agents working in parallel on different parts of the pipeline.

The total wall-clock time for the book was 8 weeks. The total in-Claude time (across all agents) was probably 200-250 hours. The total of-my-attention time was around 120-150 hours over those 8 weeks. The 50-100 hour gap is what the parallel agent dispatch produced.

What unexpectedly worked

Two things surprised me on the upside.

The Copy Editor was the highest-leverage role. I had assumed the Drafter would be the win — that "Claude writes drafts" was the meta-magic. The Drafter was helpful, but the Copy Editor was where the compounding really showed. By chapter 20, the Copy Editor was catching patterns I hadn't even consciously noticed I had until it flagged them. The book's voice consistency across 28 chapters owes more to the Copy Editor than to me.

The Typesetter saved a week. I had budgeted 5-7 days for typesetting at the end of the project. With the Typesetter running incrementally per chapter, the total typesetting time was 1 day at the end (mostly final-pass review). The incremental approach also meant that typesetting issues surfaced during writing, when fixing them was cheap (rewrite the paragraph), instead of after writing, when fixing them is expensive (the whole chapter is otherwise final).

What unexpectedly broke

Two things surprised me on the downside.

The Drafter's voice drifted in long chapters. Chapters over 4,500 words — there were three of them — produced drafts where the voice subtly degraded in the second half. The Drafter would start in my voice and end in a more generic AI voice. The fix was to dispatch the Drafter on chapter sections (one section at a time, 1,500-2,000 words) instead of whole chapters. That worked. The handoff contract had to be revised in week 4.

KDP's API documentation was wrong about hardcover spine widths. This is not the agent's fault, but the agent could not have caught it. KDP's stated formula for calculating hardcover spine width based on page count was off by 1-2mm at our exact page count. The first hardcover proof came back with a misaligned spine. The fix required manually recalculating and re-uploading the wrap PDF. The KDP Submitter has since had a "manually verify spine width on first proof" step added to its checklist, but at the cost of one wasted proof copy.

What you can copy

If you're considering a similar pipeline for any book-length artifact (book, report, course, course-companion-PDF), the five roles map cleanly to most content production. The skills change but the shape does not.

The book's Appendix C has all five Skill files I used, ready to copy into your own ~/.claude/skills/ directory. The voice rubric obviously needs to be replaced with your own voice. The typesetting Skill is specific to LaTeX + 6×9 paperback and would need a complete rewrite for any other format. The Drafter, Diagrammer, Copy Editor, and KDP Submitter Skills port more or less directly.

The full book — How to Claude — The Playbook for a One-Person Business — is on Amazon in all three formats the pipeline produced. If you want to validate the meta-claim ("this book was produced using the methodology it teaches"), Appendix B is the receipts.

Andy Garcia — solo dev, four App Store apps, one LegalTech SaaS, one book shipped via the pipeline above. The book is the full playbook.