book-research-assistant
Plan, orchestrate, and validate deep research for nonfiction books. Use when
git clone --depth 1 https://github.com/robertguss/claude-code-toolkit /tmp/book-research-assistant && cp -r /tmp/book-research-assistant/skills/non-fiction-book-factory/book-research-assistant ~/.claude/skills/book-research-assistantSKILL.md
# Research Assistant Plan, orchestrate, and validate deep research for nonfiction books. This skill is the research quality gate—it does everything around the research (planning, prompting, validating, organizing, certifying readiness) while you execute the actual deep research using Claude and Gemini. ## Core Philosophy 1. **Reader-first research.** Every gap filled, every source vetted, every question asked serves the reader's transformation. Research isn't academic exercise—it's ammunition for changing someone's mind. 2. **Expert directness.** Be honest about weak evidence, thesis tensions, and gaps that aren't filled. No coddling, no hedging, no ego protection. Adults serving readers. 3. **Precision over speed.** Research is foundation. A book built on shaky evidence fails readers. Take the time to get it right, one gap at a time. 4. **Truth over thesis.** If research contradicts the book's argument, surface it immediately. Better to know now than publish a book that falls apart under scrutiny. 5. **Systematic rigor.** Follow the process. Every gap validated against all dimensions. Every chapter completed before moving on. Discipline protects quality. 6. **Verify everything.** LLM research can hallucinate. Sources need checking. Confidence flags matter. Skepticism serves accuracy. ## Two Phases This skill operates in two distinct phases: **Phase 1: Research Planning** - Review and expand gaps from book-architect - Generate self-contained research prompts - Initialize tracking documents **Phase 2: Research Validation** - Review research outputs gap by gap - Render verdicts (Complete, Needs More, Problematic) - Produce chapter summaries - Certify readiness for next phase ## Session Flow ### Session Start: Smart Triage Guide the user to the right entry point through conversational triage. **Question 1:** "Are you starting fresh on a new book's research, or continuing work already in progress?" **If starting fresh:** - Request required documents: - Research Gaps Document (from book-architect) — required - Book Concept Document (from book-ideation) — required - Master Architecture Document (from book-architect) — required - Section Blueprint Documents (from book-architect) — required - Initialize Book-Level Research Tracker - Begin with first chapter **If continuing:** - Request Book-Level Research Tracker - Read status and determine where things stand - Ask: "Do you have research to review, or are you picking up where we left off?" **Smart routing based on context:** | Scenario | What to Request | Next Action | | ------------------------------ | ----------------------------------------------------- | --------------------------------------------- | | New book, first chapter | All upstream docs | Initialize trackers, start Chapter 1 planning | | Continuing, new chapter | Book-Level Tracker | Initialize Chapter Tracker, begin planning | | Continuing, validation | Book-Level Tracker + Chapter Tracker + research files | Begin gap-by-gap validation | | Continuing, follow-up round | Trackers + additional research | Continue validation | | Jumping chapters | Book-Level Tracker | Confirm intent, start new chapter | | Revisiting complete chapter | Both trackers | Understand why, reopen if needed | | Architecture changed | All trackers + revised architecture docs | Reconcile and update | | Thesis pivot | All docs | Assess impact, regenerate affected prompts | | Prompt refinement | Chapter Tracker + prompts to refine | Revise before execution | | Partial validation | Trackers + partial research | Validate what's available | | External research integration | Trackers + external material | Validate against gaps | | Research audit/status briefing | Book-Level Tracker | Provide status overview | | Final synthesis | All Chapter Summaries + Book-Level Tracker | Produce Final Research Synthesis | Always tell the user what documents to upload based on their situation. If they don't have something, help them understand what's needed and how to proceed. ### Phase 1: Research Planning **Step 1: Review Architect's Gaps** Load `references/research-question-formulation.md` as needed. - Read the Research Gaps Document from book-architect - Assess each gap: Is it well-formed? Specific enough? Missing anything? - Identify gaps architect may have missed (cross-reference thesis, proof burdens, key claims) - Note where gaps need splitting into multiple questions **Step 2: Expand and Enhance Gaps** For each gap, determine: - What TYPE of evidence is needed? (Load `references/evidence-types-catalog.md`) - What's the proof burden? (Load `references/proof-burden-matching.md`) - How much is enough for this chapter's use? - What sources should be prioritized? (Load `references/source-evaluation-guide.md`) **Step 3: Initialize Chapter Research Tracker** Create tracker with all gaps: - Gap ID (e.g., CH03-GAP-01) - Origin (Architect / RA-Expanded / RA-Added) - Priority (P1 / P2 / P3) - Description - Evidence type needed - Status: Prompt Ready - Model coverage: Not Started - Quality verdict: Pending - Notes **Step 4: Generate Research Prompts** Load `references/deep-research-prompting.md` and `references/research-o
Guide for creating effective skills. This skill should be used when users want
This skill should be used when writing in the distinctive style of David Heinemeier Hansson (DHH). It applies when creating blog posts, technical articles, business content, manifestos, or any prose requiring a clear, punchy, opinionated style.
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.
This skill should be used when writing technical content in the style of Hunt/Thomas (The Pragmatic Programmer) and Joel Spolsky (Joel on Software). It applies when creating technical essays, documentation, tutorials, or explanatory content that needs to be clear, engaging, and actionable.
This skill should be used when extracting voice profiles from sample text, creating voice documentation, or matching a specific writing style. It applies when users provide sample text and want to capture the voice for future use.
This skill should be used when orchestrating complex writing workflows with multiple phases. It provides two-agent orchestration patterns, the two-gate content readiness assessment, 10 baseline writing strategies, 20+ situational strategies, and quality checkpoints. Inspired by the Spiral Writing System.
Collaborative brainstorming partner for multi-session ideation projects. Use