All skills
Skillintermediate

Section Blueprint: [Section Number] — [Section Title]

**Book:** [Book Title] **Section Type:** [Narrative / Argument / Instructional / Encouragement] **Chapters:** [X-Y] **Version:** v1 **Date:** [Date]

Claude Code Knowledge Pack7/10/2026

Overview

Section Blueprint: [Section Number] — [Section Title]

Book: [Book Title]
Section Type: [Narrative / Argument / Instructional / Encouragement]
Chapters: [X-Y]
Version: v1
Date: [Date]


Section Purpose

[What this section does for the reader. What transformation happens across these chapters? Why does this section exist?]


Section Entry State

Reader arrives:

  • Believing: [What they believe at section start]
  • Feeling: [Emotional state]
  • Asking: [The question driving them into this section]

Section Exit State

Reader leaves:

  • Believing: [What has shifted]
  • Feeling: [Emotional state]
  • Ready for: [What comes next]

Chapter Blueprints


Chapter [X]: [Title]

Type: [Narrative / Argument / Instructional / Encouragement]
Weight: [Heavy / Medium / Light]
One-Line: [Brief description]

Reader's Journey

Incoming Hook:
[The question or tension pulling them into this chapter]

Reader Emotional Arc:

  • Starts: [What they believe and feel entering]
  • Ends: [What they believe and feel leaving]

Key Insight:
[The ONE thing they must walk away with—one sentence]

Outgoing Hook:
[The question or tension propelling them to next chapter]

Chapter Architecture

Purpose:
[This chapter's ONE job—complete the sentence: "This chapter's job is to _____ the reader so that they _____."]

Content:

  • [Key point / concept / evidence 1]
  • [Key point / concept / evidence 2]
  • [Key point / concept / evidence 3]
  • [...]

Through-Line Moments:

  • [Which through-line surfaces here, and how]

Structural Connections:

  • Sets up: [What this chapter establishes for later]
  • Pays off: [What earlier setup this chapter resolves]
  • Callbacks to: [References to earlier chapters]

Guardrails

What NOT to Include:

  • [Content that belongs elsewhere]
  • [Tangents to avoid]
  • [Scope boundaries]

Proof Burden Notes:
[If this chapter carries heavy claims, note what evidence is required]

Resistance Point:
[If applicable: Where might the reader disengage? What keeps them reading?]

Research Gaps:

  • [Gap ID from research-gaps.md]: [Brief description]

Chapter [X+1]: [Title]

Type: [Type]
Weight: [Weight]
One-Line: [Brief description]

Reader's Journey

Incoming Hook:
[...]

Reader Emotional Arc:

  • Starts: [...]
  • Ends: [...]

Key Insight:
[...]

Outgoing Hook:
[...]

Chapter Architecture

Purpose:
[...]

Content:

  • [...]

Through-Line Moments:

  • [...]

Structural Connections:

  • Sets up: [...]
  • Pays off: [...]
  • Callbacks to: [...]

Guardrails

What NOT to Include:

  • [...]

Proof Burden Notes:
[...]

Resistance Point:
[...]

Research Gaps:

  • [...]

[Continue for each chapter in section...]


Section Hook Chain Verification

ChapterIncoming HookOutgoing Hook
[X][Hook][Hook][ ]
[X+1][Hook—should match above outgoing][Hook][ ]
.........[ ]

Verify: Does each outgoing hook connect to the next incoming hook?


Section Pacing Check

ChapterWeightTypeNotes
[X][H/M/L][Type][Any concerns?]
[X+1][H/M/L][Type][Any concerns?]

Verify: No more than two Heavy chapters in sequence. Rhythm feels intentional.


Section Checklist

  • Every chapter has ONE clear job
  • Entry/exit states defined for all chapters
  • Hook chain flows without gaps
  • Key insights are distinct (no duplicates)
  • Pacing varies appropriately
  • Through-lines surface as planned
  • Research gaps flagged and documented
  • "What NOT to include" specified for each chapter