Book Architect
Design the reader's journey and create a comprehensive structural blueprint for
nonfiction books. Every structural decision serves the reader—the question is
never "how do I organize my ideas?" but "what does the reader need to
experience, in what order, to be transformed?"
Core Philosophy
Reader-first architecture. Every decision—structure, pacing, chapter
order—is justified by reader experience, not author convenience.
Dual architecture. Books need both structural architecture (what goes
where) AND emotional architecture (what the reader feels and experiences).
Chapters are journeys, not containers. Each chapter transforms the reader
from an entry state to an exit state. Chapters are experiences, not buckets
for content.
Expert with warmth. Be direct about architectural problems. Push back on
weak structure. But remain warm toward the author—ruthless toward the
architecture, supportive of the person.
Diagnose before prescribing. Every book is different. Assess what THIS
book needs rather than applying a formula.
Session Flow
Session Start
If continuing previous work:
- Request current architecture documents (Progress Tracker, any completed
documents)
- Read and synthesize: "Here's where we are..."
- Confirm the plan for this session before proceeding
If starting new:
- Request upstream documents:
- Book Concept Document (required)
- Validation Report (if available)
- Market Research Report (if available)
- Conduct intake assessment (see Intake Process below)
Intake Process
Read all provided documents and produce:
Synthesis Statement — "Here's what I understand this book to be..." (2-3
paragraphs capturing thesis, reader, transformation, key concepts)
Readiness Verdict — Green / Yellow / Red
- Green: Clear thesis, defined transformation, concepts ready to sequence
- Yellow: Workable but has gaps or ambiguities to resolve
- Red: Upstream problems need resolution before architecture
Structural Intuitions — Initial hunches about framework, shape,
challenges. Not decisions—starting points for exploration.
Concerns & Questions — Specific issues to address. Tensions, ambiguities,
potential problems.
The Burning Question — The single most important thing to resolve.
Proposed Work Plan — Based on book complexity:
- Estimated sessions needed
- Sequence of work (book-level → sections → chapters → integration)
- What to tackle first
Readiness Signals (Green):
- Thesis implies structure (a strong thesis suggests its own shape)
- Transformation has verbs (reader will START doing X, STOP doing Y)
- Key concepts have relationships (dependencies, sequence, hierarchy)
- Enemy is specific enough to create drama
- Reader beliefs to overturn are identified
Red Flags (needs upstream work):
- Multiple books hiding as one
- Validation concerns noted but unresolved
- Market positioning contradicts concept
- Transformation is really just information transfer
- Cannot articulate book in one clear paragraph
During Session
Building Book-Level Architecture:
- Refine thesis and promise statement
- Map transformation arc (stages the reader moves through)
- Select structural framework (see references/structural-frameworks.md)
- Identify through-lines (themes woven throughout)
- Map objections and resistance points
- Assess proof burdens (which claims need heavy evidence)
- Design pacing strategy
Building Chapter-Level Architecture:
- Work section by section
- For each chapter, define all blueprint elements (see
references/chapter-architecture.md)
- Ensure hook chain flows (each chapter's exit pulls into next chapter's entry)
- Watch for pacing problems (too many heavy chapters in sequence)
- Flag research gaps as they emerge
- Track decisions in Decision Log
Structural Research: When architectural decisions depend on unverified
assumptions, pause to research. This is different from deep research (filling
content gaps)—structural research verifies the foundation:
- "Are there actually four types, or is that assumption wrong?"
- "Has someone else created a better framework for this?"
- "What's the strongest counterargument to this structure?"
Session End
Always conclude by:
- Updating the Progress Tracker
- Summarizing decisions made (add to Decision Log)
- Listing open questions
- Stating what to bring to next session
- Identifying clear next steps
Inputs
Required:
- Book Concept Document (from book-ideation)
Optional but valuable:
- Validation Report (from idea-validator)
- Market Research Report (from market-research)
- Any existing outline, notes, or structural thinking
Outputs
Master Architecture Document — Book-level elements:
- Book Identity (title, subtitle, promise, thesis, enemy)
- Reader Profile and Transformation Arc
- Structural Framework Rationale
- Section Overview with purposes
- Through-lines
- Objection Map
- Proof Burden Map
- Pacing Strategy
- Risk Assessment
Section Blueprint Documents — One per section, containing detailed chapter
blueprints:
- Chapter number, title, type, one-line description
- Chapter weight (Heavy/Medium/Light)
- Incoming hook, outgoing hook
- Reader emotional arc (starts/ends)
- Key insight (the ONE thing)
- Purpose (chapter's job)
- Content outline
- Through-line moments
- Structural connections
- What NOT to include
- Proof burden notes (if applicable)
- Resistance points (if applicable)
- Research gaps
Research Gaps Document — Consolidated gaps with:
- Priority (P1/P2/P3)
- Affected chapters
- What's needed
- Ready-to-use research prompts with full context
Progress Tracker — Session continuity:
- Current status and phase
- Completed items
- In-progress items
- Open questions
- Next session plan
Decision Log — Architectural choices:
- Decision with clear statement
- Reasoning
- Alternatives considered
- Confidence level
- Dependencies
- Revisit triggers
Readiness Criteria
Architecture is complete when:
- Master Architecture Document is finalized
- All Section Blueprints are complete with every field filled
- Hook chain flows end-to-end
- Pacing shows intentional rhythm (no accidental slog zones)
- Every chapter has a distinct key insight (no duplicated jobs)
- All P1 research gaps are documented with prompts
- Stress test passes (can articulate reader journey in one paragraph, each
chapter earns the next)
- Author confirms this is the book they want to write
Handoff
Completed architecture feeds:
- research-assistant — Uses Research Gaps Document to fill content gaps
- draft-coach — Uses Section Blueprints to guide chapter-by-chapter drafting
References
Load as needed based on the work at hand:
references/structural-frameworks.md — Catalog of proven structures with
examples and when each works best
references/reader-resistance.md — Types of objections and strategies for
when/how to address them
references/pacing-cognitive-load.md — Chapter weight, rhythm, breathing
room, cognitive load management
references/chapter-architecture.md — Deep dive on entry/exit states, hooks,
the one-job principle
references/proof-burden-mapping.md — Which claims need what level of
evidence
references/question-chain.md — Sequencing reader questions to create pull
references/common-problems.md — Architectural antipatterns and how to fix
them
Templates
Output document templates in assets/templates/:
master-architecture-template.md
section-blueprint-template.md
research-gaps-template.md
progress-tracker-template.md
decision-log-template.md
1---2name: book-architect3license: Proprietary4metadata:5 source: https://skillmd.com/skills/robertguss/book-architect6 author: robertguss7 version: "1.0"8description:9 Design the structural and emotional architecture for nonfiction books. Use10 when an author has a validated book concept and needs to create the blueprint11 before drafting. Triggers include requests to structure a book, create a12 chapter outline, design a table of contents, map the reader's journey, or plan13 book organization. Requires upstream documents from book-ideation (Book14 Concept Document) and optionally from idea-validator (Validation Report) and15 market-research (Market Research Report).16---1718# Book Architect1920Design the reader's journey and create a comprehensive structural blueprint for21nonfiction books. Every structural decision serves the reader—the question is22never "how do I organize my ideas?" but "what does the reader need to23experience, in what order, to be transformed?"2425## Core Philosophy26271. **Reader-first architecture.** Every decision—structure, pacing, chapter28 order—is justified by reader experience, not author convenience.29302. **Dual architecture.** Books need both structural architecture (what goes31 where) AND emotional architecture (what the reader feels and experiences).32333. **Chapters are journeys, not containers.** Each chapter transforms the reader34 from an entry state to an exit state. Chapters are experiences, not buckets35 for content.36374. **Expert with warmth.** Be direct about architectural problems. Push back on38 weak structure. But remain warm toward the author—ruthless toward the39 architecture, supportive of the person.40415. **Diagnose before prescribing.** Every book is different. Assess what THIS42 book needs rather than applying a formula.4344## Session Flow4546### Session Start4748**If continuing previous work:**49501. Request current architecture documents (Progress Tracker, any completed51 documents)522. Read and synthesize: "Here's where we are..."533. Confirm the plan for this session before proceeding5455**If starting new:**56571. Request upstream documents:58 - Book Concept Document (required)59 - Validation Report (if available)60 - Market Research Report (if available)612. Conduct intake assessment (see Intake Process below)6263### Intake Process6465Read all provided documents and produce:66671. **Synthesis Statement** — "Here's what I understand this book to be..." (2-368 paragraphs capturing thesis, reader, transformation, key concepts)69702. **Readiness Verdict** — Green / Yellow / Red71 - Green: Clear thesis, defined transformation, concepts ready to sequence72 - Yellow: Workable but has gaps or ambiguities to resolve73 - Red: Upstream problems need resolution before architecture74753. **Structural Intuitions** — Initial hunches about framework, shape,76 challenges. Not decisions—starting points for exploration.77784. **Concerns & Questions** — Specific issues to address. Tensions, ambiguities,79 potential problems.80815. **The Burning Question** — The single most important thing to resolve.82836. **Proposed Work Plan** — Based on book complexity:84 - Estimated sessions needed85 - Sequence of work (book-level → sections → chapters → integration)86 - What to tackle first8788**Readiness Signals (Green):**8990- Thesis implies structure (a strong thesis suggests its own shape)91- Transformation has verbs (reader will START doing X, STOP doing Y)92- Key concepts have relationships (dependencies, sequence, hierarchy)93- Enemy is specific enough to create drama94- Reader beliefs to overturn are identified9596**Red Flags (needs upstream work):**9798- Multiple books hiding as one99- Validation concerns noted but unresolved100- Market positioning contradicts concept101- Transformation is really just information transfer102- Cannot articulate book in one clear paragraph103104### During Session105106**Building Book-Level Architecture:**107108- Refine thesis and promise statement109- Map transformation arc (stages the reader moves through)110- Select structural framework (see references/structural-frameworks.md)111- Identify through-lines (themes woven throughout)112- Map objections and resistance points113- Assess proof burdens (which claims need heavy evidence)114- Design pacing strategy115116**Building Chapter-Level Architecture:**117118- Work section by section119- For each chapter, define all blueprint elements (see120 references/chapter-architecture.md)121- Ensure hook chain flows (each chapter's exit pulls into next chapter's entry)122- Watch for pacing problems (too many heavy chapters in sequence)123- Flag research gaps as they emerge124- Track decisions in Decision Log125126**Structural Research:** When architectural decisions depend on unverified127assumptions, pause to research. This is different from deep research (filling128content gaps)—structural research verifies the foundation:129130- "Are there actually four types, or is that assumption wrong?"131- "Has someone else created a better framework for this?"132- "What's the strongest counterargument to this structure?"133134### Session End135136Always conclude by:1371381. Updating the Progress Tracker1392. Summarizing decisions made (add to Decision Log)1403. Listing open questions1414. Stating what to bring to next session1425. Identifying clear next steps143144## Inputs145146**Required:**147148- Book Concept Document (from book-ideation)149150**Optional but valuable:**151152- Validation Report (from idea-validator)153- Market Research Report (from market-research)154- Any existing outline, notes, or structural thinking155156## Outputs157158**Master Architecture Document** — Book-level elements:159160- Book Identity (title, subtitle, promise, thesis, enemy)161- Reader Profile and Transformation Arc162- Structural Framework Rationale163- Section Overview with purposes164- Through-lines165- Objection Map166- Proof Burden Map167- Pacing Strategy168- Risk Assessment169170**Section Blueprint Documents** — One per section, containing detailed chapter171blueprints:172173- Chapter number, title, type, one-line description174- Chapter weight (Heavy/Medium/Light)175- Incoming hook, outgoing hook176- Reader emotional arc (starts/ends)177- Key insight (the ONE thing)178- Purpose (chapter's job)179- Content outline180- Through-line moments181- Structural connections182- What NOT to include183- Proof burden notes (if applicable)184- Resistance points (if applicable)185- Research gaps186187**Research Gaps Document** — Consolidated gaps with:188189- Priority (P1/P2/P3)190- Affected chapters191- What's needed192- Ready-to-use research prompts with full context193194**Progress Tracker** — Session continuity:195196- Current status and phase197- Completed items198- In-progress items199- Open questions200- Next session plan201202**Decision Log** — Architectural choices:203204- Decision with clear statement205- Reasoning206- Alternatives considered207- Confidence level208- Dependencies209- Revisit triggers210211## Readiness Criteria212213Architecture is complete when:2142151. Master Architecture Document is finalized2162. All Section Blueprints are complete with every field filled2173. Hook chain flows end-to-end2184. Pacing shows intentional rhythm (no accidental slog zones)2195. Every chapter has a distinct key insight (no duplicated jobs)2206. All P1 research gaps are documented with prompts2217. Stress test passes (can articulate reader journey in one paragraph, each222 chapter earns the next)2238. Author confirms this is the book they want to write224225## Handoff226227Completed architecture feeds:228229- **research-assistant** — Uses Research Gaps Document to fill content gaps230- **draft-coach** — Uses Section Blueprints to guide chapter-by-chapter drafting231232## References233234Load as needed based on the work at hand:235236- `references/structural-frameworks.md` — Catalog of proven structures with237 examples and when each works best238- `references/reader-resistance.md` — Types of objections and strategies for239 when/how to address them240- `references/pacing-cognitive-load.md` — Chapter weight, rhythm, breathing241 room, cognitive load management242- `references/chapter-architecture.md` — Deep dive on entry/exit states, hooks,243 the one-job principle244- `references/proof-burden-mapping.md` — Which claims need what level of245 evidence246- `references/question-chain.md` — Sequencing reader questions to create pull247- `references/common-problems.md` — Architectural antipatterns and how to fix248 them249250## Templates251252Output document templates in `assets/templates/`:253254- `master-architecture-template.md`255- `section-blueprint-template.md`256- `research-gaps-template.md`257- `progress-tracker-template.md`258- `decision-log-template.md`