What problem does it solve? Turning scattered ideas, blog posts, or notes into a coherent 60,000-word non-fiction book is hard: premises drift, chapters repeat each other, and drafts stall without a clear architecture. This Skill provides a disciplined framework for defining a core premise, structuring chapters, sustaining narrative voice, and revising systematically. ## Core Features & Use Cases - Core Premise & Reader Contract: Formulate a single-sentence organizing idea and define the reader's before-and-after transformation arc. - 10-Chapter Architecture: Apply a 3-act structure with a fractal chapter template covering hook, concept, implementation, objections, and summary. - 3-Pass Revision Methodology: Run separate structural, argument-level, and line-editing passes to polish the full manuscript. - Use Case: A senior engineer wants to write a book on software reliability. Use this Skill to produce a BOOK-PROPOSAL.md with a one-sentence thesis, competitive title analysis, and a chapter-by-chapter outline with case study anchors. ## Quick Start Use the book-writing skill to turn my notes on engineering leadership into a structured 10-chapter book proposal with a core premise and chapter outline.
