--- title: "The Book Factory: Complete Reference Guide" description: "**Purpose:** This document captures the complete vision, philosophy, and specifications for a suite of Claude skills that replicate the traditional publishing infrastructure for nonfiction book creation. Use this to brief future Claude sessions when building individual skills." type: skill canonical_url: https://claudary.paisolsolutions.com/skills/book-factory-reference source: "Claudary" difficulty: intermediate author: "Claude Code Knowledge Pack" date: 2026-07-10T11:08:30.636Z license: CC-BY-4.0 attribution: "The Book Factory: Complete Reference Guide — Claudary (https://claudary.paisolsolutions.com/skills/book-factory-reference)" --- # The Book Factory: Complete Reference Guide **Purpose:** This document captures the complete vision, philosophy, and specifications for a suite of Claude skills that replicate the traditional publishing infrastructure for nonfiction book creation. Use this to brief future Claude sessions when building individual skills. ## Overview # The Book Factory: Complete Reference Guide **Purpose:** This document captures the complete vision, philosophy, and specifications for a suite of Claude skills that replicate the traditional publishing infrastructure for nonfiction book creation. Use this to brief future Claude sessions when building individual skills. **Author:** Robert Guss **Created:** December 29, 2025 **Last Updated:** December 29, 2025 --- ## Table of Contents 1. [Overview & Philosophy](#overview--philosophy) 2. [The Factory Pipeline](#the-factory-pipeline) 3. [Phase 0: Raw Ideation](#phase-0-raw-ideation) 4. [Phase 1: Book Concept Development](#phase-1-book-concept-development) 5. [Phase 2: Validation](#phase-2-validation) 6. [Phase 3: Architecture](#phase-3-architecture) 7. [Phase 4: Deep Research](#phase-4-deep-research) 8. [Phase 5: Drafting](#phase-5-drafting) 9. [Phase 6: Editing Pipeline](#phase-6-editing-pipeline) 10. [Phase 7: Production](#phase-7-production) 11. [Cross-Cutting Principles](#cross-cutting-principles) 12. [Skill Design Standards](#skill-design-standards) --- ## Overview & Philosophy ### The Core Insight Traditional publishing provides authors with a team of specialized experts: developmental editors, copy editors, fact-checkers, indexers, and more. Self-published authors typically lack access to this infrastructure, resulting in books that suffer from preventable weaknesses. This skill suite replicates that infrastructure using Claude, creating a "book factory" with specialized skills for each phase of the book creation process. ### Guiding Principles 1. **Every decision serves the reader.** The question is never "what do I want to say?" but "what transformation does the reader need, and how can this book deliver it?" 2. **Optimize for the reader's experience.** Structure, pacing, clarity, and engagement are all evaluated from the reader's perspective. 3. **Skills hand off to each other.** Each skill produces structured output that the next skill consumes. This creates a consistent, repeatable workflow. 4. **Validate before investing.** The pipeline includes explicit validation gates to prevent wasted effort on books that won't succeed. 5. **Nonfiction only.** This factory is designed specifically for nonfiction books. Fiction requires different approaches. ### The Author Context Robert Guss is: - A technologist at Westminster Theological Seminary - An elder in the Orthodox Presbyterian Church - Grounded in Reformed theology and Van Tillian presuppositional apologetics - Self-publishes through Amazon KDP - Working on multiple book projects, with "Thinking with Paper" (about Luhmann's Zettelkasten method) being the most developed --- ## The Factory Pipeline ``` ┌─────────────────────────────────────────────────────────────────────────┐ │ THE BOOK FACTORY │ ├─────────────────────────────────────────────────────────────────────────┤ │ │ │ PHASE 0: RAW IDEATION (Optional starting point) │ │ ┌─────────────┐ │ │ │ brainstorm │ ✅ Done — Generic, multi-purpose │ │ └──────┬──────┘ │ │ │ │ │ ▼ │ │ PHASE 1: BOOK CONCEPT DEVELOPMENT │ │ ┌────────────────┐ │ │ │ book-ideation │ ✅ Done — Nonfiction-specific concept development │ │ └───────┬────────┘ │ │ │ Outputs: Book Concept Document │ │ ▼ │ │ PHASE 2: VALIDATION (Go/No-Go Decision) │ │ ┌─────────────────┐ ┌──────────────────┐ │ │ │ idea-validator │────▶│ market-research │ │ │ │ (Research check)│ │ (KDP viability) │ │ │ └────────┬────────┘ └────────┬─────────┘ │ │ │ │ │ │ └───────────┬───────────┘ │ │ ▼ │ │ [GO/NO-GO GATE] │ │ │ │ │ ▼ │ │ PHASE 3: ARCHITECTURE │ │ ┌─────────────────┐ │ │ │ book-architect │ │ │ └────────┬────────┘ │ │ │ Outputs: Reader Journey, Chapter Blueprint, TOC │ │ ▼ │ │ PHASE 4: DEEP RESEARCH │ │ ┌────────────────────┐ │ │ │ research-assistant │ (Fills gaps identified by architect) │ │ └────────┬───────────┘ │ │ │ │ │ ▼ │ │ PHASE 5: DRAFTING │ │ ┌─────────────┐ │ │ │ draft-coach │ │ │ └──────┬──────┘ │ │ │ │ │ ▼ │ │ PHASE 6: EDITING PIPELINE │ │ ┌───────────────────────┐ │ │ │ developmental-editor │ │ │ └───────────┬───────────┘ │ │ ▼ │ │ ┌───────────────────────┐ │ │ │ line-editor │ │ │ └───────────┬───────────┘ │ │ ▼ │ │ ┌───────────────────────┐ │ │ │ copy-editor │ │ │ └───────────┬───────────┘ │ │ ▼ │ │ ┌───────────────────────┐ │ │ │ fact-checker │ │ │ └───────────┬───────────┘ │ │ ▼ │ │ ┌───────────────────────┐ │ │ │ proofreader │ │ │ └───────────┬───────────┘ │ │ │ │ │ ▼ │ │ PHASE 7: PRODUCTION │ │ ┌───────────────────────┐ │ │ │ indexer │ │ │ └───────────────────────┘ │ │ │ └─────────────────────────────────────────────────────────────────────────┘ ``` --- ## Phase 0: Raw Ideation ### Skill: `brainstorm` **Status:** ✅ Complete **Location:** `claude-skills/brainstorm/` **Purpose:** Generic, multi-purpose brainstorming for any creative or analytical challenge. Not book-specific. **Key Features:** - Multi-session continuity via versioned markdown documents - 25+ brainstorming methods catalog - Connected mode (cross-project awareness) vs. clean-slate mode - Idea maturity tracking (Raw → Developing → Refined → Ready → Parked → Eliminated) - Disagreement protocol and decision logging **Outputs:** - Versioned brainstorm documents - Parking lot for cross-project ideas - Decision log with reasoning **Handoff:** Raw brainstorm documents feed into `book-ideation` for nonfiction-specific development. --- ## Phase 1: Book Concept Development ### Skill: `book-ideation` **Status:** ✅ Complete **Location:** `claude-skills/book-ideation/` **Purpose:** Transform raw ideas into structured nonfiction book concepts. Bridges the gap between generic brainstorming and book architecture by developing eight fundamental elements that determine whether a book should exist and what it must accomplish. **The Eight Elements:** | Element | Core Question | | --------------------- | --------------------------------------------------------------------------------------- | | 1. The Reader | Who specifically is this for? (Beyond demographics—their situation, beliefs, struggles) | | 2. The Transformation | Where will they be after reading? (Before/after states) | | 3. The Core Thesis | What's the one big idea? (Must be a claim someone can disagree with) | | 4. The Author Angle | Why are you the one to write this? (Experience, expertise, access, perspective) | | 5. The Stakes | Why does this matter? Why now? (Cost of inaction, timeliness) | | 6. The Key Concepts | What are the 3-7 major ideas supporting the thesis? | | 7. The Enemy | What is this book arguing against? (Mindset, practice, conventional wisdom) | | 8. The Promise | In one sentence, what does the reader get? | **Key Features:** - Multi-session development with versioned documents - Collaboration behaviors (surface insights, challenge weakness, push for specificity) - Quick Capture Mode for rapid ideas - Readiness criteria for downstream handoff - Nonfiction structural frameworks reference **Inputs:** - Raw idea (one sentence) - Brainstorm document - Zettelkasten notes - Existing partial concept **Outputs:** - Book Concept Document (versioned, with all eight elements and readiness assessment) **Handoff:** Book Concept Document feeds into `idea-validator` and `market-research`. --- ## Phase 2: Validation This phase answers two critical questions before significant investment: 1. **Is the thesis intellectually sound?** (idea-validator) 2. **Is this book commercially viable?** (market-research) ### Skill: `idea-validator` **Status:** ⬜ Not yet built **Purpose:** Stress-test the core ideas from the Book Concept Document against existing research before committing to architecture and drafting. **Key Activities:** - Identify the 3-5 core claims/theses from the Book Concept Document - Research each claim: What does existing literature say? Are there counterarguments? - Flag weak spots, contradictions, areas needing more evidence - Identify what's genuinely novel vs. well-trodden ground - Surface related ideas, frameworks, or thinkers the author may not be aware of - Assess the strength of the author's angle—is there a credibility gap? **Inputs:** - Book Concept Document (from `book-ideation`) **Outputs:** - Validation Report containing: - Confidence levels for each core claim (Strong / Needs Work / Weak) - Research bibliography for promising threads - "Kill signals" — reasons this book might fail intellectually - "Green lights" — what makes this idea strong and timely - Recommended revisions to thesis or key concepts - List of experts, books, or sources to engage with **Design Considerations:** - Should use web search to find current research, competing books, expert opinions - Must be honest about weaknesses—the goal is to surface problems early, not validate ego - Should distinguish between "this needs more research" vs. "this thesis is fundamentally flawed" **Handoff:** Validation Report informs Go/No-Go decision and feeds into `market-research`. --- ### Skill: `market-research` **Status:** ⬜ Not yet built **Purpose:** Determine if this book is worth writing from a business perspective, specifically for Amazon KDP self-publishing. **Key Activities:** - Define the target reader precisely (refine from Book Concept Document) - Analyze Amazon KDP competition: - Search for similar books by keyword - Assess their rankings, review counts, ratings - Read reviews to identify what readers praise and complain about - Identify gaps in the market - Analyze pricing strategies - Estimate market size and realistic sales potential - Recommend positioning, pricing, title/subtitle direction - Assess platform fit: Does this book align with the author's existing audience (newsletter, social media)? - Evaluate timing: Is there a trend or moment that makes this book timely? **Inputs:** - Book Concept Document (from `book-ideation`) - Validation Report (from `idea-validator`) **Outputs:** - Market Research Report containing: - Market viability scorecard (1-10 with criteria) - Competitive landscape analysis (top 5-10 competing titles) - Reader persona (refined and detailed) - Positioning recommendation (how to differentiate) - Pricing recommendation - Title/subtitle suggestions based on market analysis - Platform fit assessment - Go/No-Go recommendation with rationale **Design Considerations:** - Must use web search to access Amazon, analyze real books - Should be realistic, not optimistic—better to kill a bad idea early - Consider the author's goals: Is this book for income, authority-building, or passion? - KDP-specific considerations: categories, keywords, description optimization **Handoff:** Market Research Report informs Go/No-Go decision. If Go, both reports feed into `book-architect`. --- ### The Go/No-Go Gate After validation, the author makes an explicit decision: - **GO:** Proceed to architecture with confidence - **REVISE:** Return to `book-ideation` to address weaknesses - **KILL:** Abandon this b --- Source: [Claudary](https://claudary.paisolsolutions.com/skills/book-factory-reference) · https://claudary.paisolsolutions.com