How to Publish a Book on Amazon KDP Without a Formatter or a Designer

Once the manuscript exists, publishing is a file problem. You need a print-ready interior at a trim size you chose, a cover wrap sized to the book you actually printed, a package Amazon's automated review accepts, and a Kindle file. Write Books runs each of those as a command your agent executes, and it is honest about the one part nobody can do for you: the upload itself is manual, and your agent walks you through it.

Why does this half of the book stall so many people?

The draft is the part everybody talks about. The part that actually kills books is what comes after. The old path runs through vendors: a formatter for the interior, a designer for the cover, separate invoices from each, and then a week fighting KDP's upload errors because something came back at the wrong size. Two of those vendors bill you before you have sold a single copy, and neither of them is fast.

The Write Books pack replaces that stretch with commands. Each one produces a file, not advice. Here is what comes out of each, and what is still yours to do.

What does the print-ready interior step actually produce?

/generate-pdfs takes the markdown chapters your writer agents merged and turns them into a print-ready interior at whatever trim size you picked, with a cover page on the front. Two things run alongside the conversion that a cheap formatting job skips. The first is a table audit, because a table that runs wider than the page is one of the quiet ways an interior comes back wrong. The second is a postflight check on the finished PDF, which is the difference between believing the file is good and knowing it.

Trim size is your call, and it is the one decision here that is genuinely yours to make rather than delegate. The DaD Papers ran at two of them, because a single book and a three-book omnibus do not want the same shape.

How do you get a cover without hiring a designer?

/book-cover produces front cover concepts drawn from your book bible, with the title rendered legibly. That second clause is the whole trick. Image generators are good at atmosphere and bad at type; a beautiful cover with a mangled title is a cover you cannot use, and most people find that out after they have paid for it.

Then the wrap math. A print cover is not a picture of the front. It is one flat piece that has to cover the back, the spine and the front of the specific book you just generated, which is why the cover comes after the interior and not before it. /book-cover hands you the exact KDP wrap dimensions for that book, so the cover file is built to fit rather than built and then fought with.

What is in the KDP package?

/kdp-package is the assembly step. It puts together the interior PDF, the cover wrap, and the metadata CSV that Amazon's automated review accepts, as one package. The target here is narrow and specific: get through the automated check on the first pass instead of the third. The pack ships the troubleshooting from real runs alongside it, including the KDP rejections, the Calibre reflow failures and the LaTeX font traps that produced those rejections in the first place.

Paperback and hardcover are two packages, not one, because the wraps differ. The DaD Papers has both.

What about the Kindle file?

/kindle converts the book to AZW3 and syncs it to your own device over USB. Nothing goes through the Amazon cloud to get there, which matters more than it sounds, because this is also how you should be reading your own draft.

Put the draft on your Kindle, read it with a voice recorder going, and say your notes out loud as they come. Transcribe the voice note, hand it to your agent, and it keeps revising until it sounds like you.

That is the editor's pass, and it is the reason the Kindle step is not just an output format. You read like a reader, not like an author hunched over a laptop, and your agent takes the notes from there.

Do you want the metadata stripped?

/notrace is optional and it does one thing: it strips metadata and fingerprints from every file you distribute. Some people care about what is embedded in a PDF they send out. If you do not, skip it. It is there because the answer should be yours rather than a default someone else picked.

How does the audiobook get made?

/audiobook writes the narration script first, then renders it chapter by chapter on your own ElevenLabs account. Script before render is the order that matters: an audiobook script is not the manuscript read aloud, and the chapter-by-chapter structure means a fix to chapter nine costs you chapter nine, not the whole book.

The ACX upload is manual, the same way the Amazon upload is. The command walks you through it. The DaD Papers trilogy went all the way through this and the finished audiobook is playing inside Optimus University.

What does one trilogy turn into?

Here is the full output of the worked example, so you can see the shape of what the production half produces. Three books on distinction, decision and delight, each written independently and then combined into an omnibus. Individual PDFs at two trim sizes. Paperback and hardcover packages with different cover wraps. Four Kindle files. An audiobook script, then the audiobook.

Count the vendors that would have touched that under the old process, then count the invoices. The point is not that a machine did it. The point is that the same pipeline ran six times without six negotiations, and the books exist. Write Books is the pipeline that produced them, packaged so your agent can run it on your book.

So what is left for you to do?

Four things, and they are the right four. You decide the trim size. You pick the cover concept. You read the draft the way an editor reads it. And you do the two uploads, to Amazon and to ACX, with your agent talking you through the screens. Everything between those decisions is a command.

That is the honest version of publishing without a formatter or a designer. Not nobody does the work. Not you do the work. Your agent does the hundred hours of production, and you keep the handful of judgment calls that were always going to be yours.

Common questions

Do I need a cover designer?

No. /book-cover produces front cover concepts from your book bible with the title rendered legibly, plus the exact KDP wrap dimensions for the book you actually printed. You pick the concept you want. The pack includes cover generation; there is no separate designer invoice.

Does my agent upload the book to Amazon for me?

No. The Amazon upload itself is a manual step, and your agent walks you through it. The same is true of the ACX upload for audiobooks. What the pipeline hands you is the package: the interior PDF, the cover wrap, and the metadata CSV that Amazon accepts.

What do I need installed to run the production commands?

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. There are no tokens and no credits on top; the pipeline runs on the agent you already have.

Can one manuscript produce paperback, hardcover, Kindle and audio?

Yes, and the DaD Papers are the worked example. Three books on distinction, decision and delight, each written independently and then combined into an omnibus. Individual PDFs at two trim sizes. Paperback and hardcover packages with different cover wraps. Four Kindle files. An audiobook script, then the audiobook.