| type | skill |
| lifecycle | stable |
| inheritance | inheritable |
| name | book-launch-content |
| description | Generate launch-companion content for books — blog posts, author notes, and dogfooding angles that demonstrate the book's thesis through its own production. Use when a manuscript is approaching publication submission (KDP, agent query, prelaunch). |
| tier | standard |
| applyTo | **/books/**,**/manuscript*,**/*launch*content*,**/*book*launch* |
| currency | "2026-04-25T00:00:00.000Z" |
Book Launch Content
Companion-content patterns for book launches — find the angle that demonstrates the thesis instead of summarizing it.
When to Use
- A book is approaching publication submission (KDP upload, agent query, prelaunch site)
- The author needs blog posts, author notes, or social copy that defend the manuscript without restating it
- A meditation surfaces "the manuscript already does the thing it argues for" — that's a launch angle
Trigger Phrases
- "I need a launch post for [book]"
- "What's the angle for the prelaunch?"
- "How do I write the author's note?"
- "The book argues X — does the manuscript itself do X?"
Core Pattern: Dogfood the Thesis
The strongest launch content is proof-by-production: the manuscript's own build pipeline, editing process, or research method enacts the thesis the book argues for.
| Book argues for... | Manuscript can dogfood by... |
|---|
| Forcing functions / verification habits | A pre-build linter that scans the manuscript's prose for the failure modes the book describes |
| Test-driven thinking | A test suite over the manuscript's claims (each chapter has assertions) |
| Anti-AI prose patterns | A scanner that flags AI-fingerprint phrasing in the manuscript itself |
| Reproducible research | A make book pipeline that rebuilds figures from raw data each run |
| Plain-language communication | A readability gate (Flesch/Gunning Fog threshold) in the build |
| Visible uncertainty | Confidence stamps on every chapter's claims |
If the book's thesis can be applied to its own production process, do that visibly, then write about doing it. The story becomes the strongest possible blurb defense.
Inventory Step
Before drafting any launch content, ask:
- What is the book's central thesis? (One sentence.)
- What does the manuscript ship with that proves the thesis is taken seriously by the author?
- Is there a production tool, gate, ritual, or constraint the author followed that embodies the thesis?
- If yes — that's the launch angle. If no — flag it. The book may need a dogfood-step before launch.
Pattern Catalog
1. Dogfooding (apply thesis to manuscript)
The manuscript's own pipeline enacts the thesis. Author writes about the production move, not the book's content.
Template hook: "I wrote a book about [thesis]. Then I made the book [enact thesis] itself."
2. Reflexive Narrative (process becomes anecdote)
The author's research process — what surprised them, what failed, what changed their mind — becomes a first-person companion piece. Doubles as a future-edition appendix.
Template hook: "Here's what I thought when I started this book. Here's what changed."
3. Companion-Site Bridge (book ↔ web round-trip)
Web post links to a chapter; chapter links to a deeper online treatment. Creates discovery in both directions.
Template hook: A blog post that says "Chapter N goes deeper on [X]. Here's the short version with [extra: code, video, dataset] you can't fit in print."
4. Constraint Confession
The author admits a constraint they imposed on themselves (word count cap, no AI assistance, no second-person, single-source citations) and shows what it cost. Demonstrates rigor without claiming it.
Beat Structure for Launch Posts
Use this six-beat structure for the primary launch blog post:
| Beat | Purpose | Length |
|---|
| Hook | One vivid moment that shows the thesis in action | 1 paragraph |
| Stakes | Why this matters now (the world's failure mode) | 1-2 paragraphs |
| Move | What the author did differently (the dogfood step) | 2-3 paragraphs |
| Twist | The surprise — what the move revealed that the author didn't expect | 1-2 paragraphs |
| Lesson | What readers can take away even without buying the book | 1 paragraph |
| Closing | Soft pointer to the book + companion site | 1 paragraph |
Total: 600-1,200 words. Longer drowns the angle.
Anti-Patterns
| Don't | Why |
|---|
| Summarize the book's argument | Readers can read the table of contents |
| Quote multiple chapters | Bait-and-switch — they came for an angle, not a sampler |
| Lead with "Buy my book" | Trust the angle to do the selling |
| Use AI-fingerprint phrasing | If the book argues against it, the launch post must not commit it |
| Write generic "writing process" content | Every author has one; the dogfood angle is what differentiates |
| Promise a series before shipping the first post | Commit to one strong post, expand if it lands |
Cross-References
blog-writer — execution mechanics (file naming, banner generation, publishing)book-publishing — KDP/launch timing and trim sizesai-writing-avoidance — prose patterns to avoid (especially relevant if the book itself argues against AI fingerprints)executive-storytelling — narrative arc principleslearned-patterns.instructions.md — "Dogfood your book's thesis on its own manuscript"
Checklist
Before publishing a launch companion post:
