book-writing

Files (3)

• SKILL.md
• book-writing.skill
• routing.yaml · evals/

SKILL.md (first lines)

# book-writing

## Core Philosophy
Writing a non-fiction book is not expanding a 1,000-word blog post with 200 pages of repetitive filler. A book is an extended cognitive journey that fundamentally shifts how the reader perceives reality. Sustaining reader momentum across 60,000 words requires an undeniable core premise, a disciplined chapter architecture, a consistent narrative voice, and a systematic multi-pass developmental revision process.

---

## 4-Step Non-Fiction Book Crafting Architecture

### Step 1: The Core Premise & Reader Contract
1. **The Single Organizing Idea (SOI)**:
   - Formulate the book's foundational argument in strictly one sentence:
     - Example: *"Software reliability is an organizational culture problem that cannot be solved by purchasing more monitoring tools."*
   - If the premise requires a paragraph of explanation, the thesis is unfocused.
2. **The Reader Transformation Contract**:
   - Explicitly define: Who is the reader at Chapter 1 (Current Pain & Mental Model) vs who do they become by Chapter 10 (Transformed Capability & Worldview)?

### Step 2: Macro Chapter Architecture (The 10-Chapter Arc)
1. **The 3-Act Non-Fiction Structure**:
   - *Act I: The Broken Paradigm (Chapters 1–2)*: The status quo, why current solutions fail, the true cost of inaction.
   - *Act II: The New Framework (Chapters 3–7)*: The core methodology, core mechanisms, worked case studies, and counter-intuitive principles.
   - *Act III: Mastery & Implementation (Chapters 8–10)*: Organizational rollout, handling edge cases, future evolution.
2. **The Fractal Chapter Template (4,000–6,000 words)**:
   - *The Hook & Narrative Case Study* (1,000 words): Human drama, visceral stakes.
   - *The Conceptual Breakthrough* (1,500 words): The mental model and framework diagram.
   - *Actionable Implementation & Proof* (2,000 words): Concrete steps, code/data evidence.
   - *Objections & Counter-Arguments* (800 words): Dismantling skeptic rebuttals.
   - *Chapter Summary & Action Checklist* (200 words).

### Step 3: Sustaining Narrative Velocity & Voice
1. **Show vs Tell with Sensory Grounding**:
   - Ground abstract theories in physical reality: names, timestamps, exact dollar figures, terminal error messages, room temperatures.
2. **The "One Major Idea Per Chapter" Rule**:
   - Never introduce competing conceptual models within a single chapter. Subordinate all research and anecdotes to that chapter's primary thesis.

### Step 4: The 3-Pass Revision Methodology
1. **Pass 1: Structural & Developmental Edit**:
   - Audit chapter order, identify logical gaps, cut redundant chapters entirely.
2. **Pass 2: The Scene & Argument Polish**:
   - Strengthen case study evidence; sharpen analytical frameworks.
3. **Pass 3: Line & Rhythm Edit**:
   - Read aloud to identify clumsy phrasing, varying sentence cadence and killing weak passive verbs.

---

## Deliverable Format: Book Proposal & Architecture Blueprint (`BOOK-PROPOSAL.md`)

```markdown
# Non-Fiction Book Proposal & Architecture: [Working Title]

## 1. Core Thesis & Target Reader
- **Working Title**: [Title: Subtitle]
- **Core Premise (1 Sentence)**: [Single organizing idea]
- **Target Audience**: [Specific professional persona, e.g. Senior Engineering Leaders]
- **Target Word Count**: 55,000 words (10 Chapters @ ~5,500 words/chapter)

## 2. Competitive Title Analysis
- *Book A (Competitor)*: Strong on theory, lacks tactical code/architecture examples.
- *Our Differentiation*: Practical engineering playbook with real post-mortems and code.

## 3. Chapter-by-Chapter Architecture
### Chapter 1: The Illusion of Microservice Velocity
- **Core Argument**: Microservices adopted prematurely introduce distributed systems latency without organizational benefits.
- **Narrative Anchor Case Study**: The 2024 Black Friday outage at [Fintech Startup].
- **Key Framework**: The Distributed Complexity Tipping Point Matrix.

### Chapter 2: The Modular Monolith Alternative
- **Core Argument**: In-process domain isolation provides microservice boundaries with zero network latency.
- **Key Framework**: The Hexagonal Architecture boundary design.
```

---

## Worked Example: Technical Architecture Book Outlining

- **Thesis**: "Observability without automated remediations creates alert fatigue that slows incident recovery."
- **Execution**: Structured 8 chapters. Chapter 3 detailed a true enterprise outage where 1,400 Slack alerts fired in 3 minutes, paralyzing on-call engineers.
- **Outcome**: Secured literary agent and top publisher contract based on a 15-page proposal and 2 sample chapters.

---

## Verification Checklist

- [ ] Core premise is formulated in a single, falsifiable declarative sentence.
- [ ] Every chapter follows a consistent fractal structure with real case studies.
- [ ] Explicit reader transformation arc (Before vs After) is defined.
- [ ] Competitive book analysis outlines clear differentiation.
- [ ] Revision methodology includes separate structural, argument, and line editing passes.

---

## Anti-Patterns

- **The Blog Anthology**: Stapling 15 unrelated blog posts together and calling it a book.
- **Scope Explosion**: Trying to explain the entire history of computing instead of solving one specific problem.
- **Writing Without Outlining**: Writing 30,000 words before realizing Chapter 4 contradicts Chapter 1.

From poorvith-mp/skills-writing, MIT.

More from poorvith-mp/skills-writing