Book Reader Conversations
Core Lens
Reader conversations are product discovery for useful nonfiction. The goal is not to ask whether people like a book idea. The goal is to understand the reader's real situation, language, failed attempts, urgency, objections, and ability to receive the value the book intends to deliver.
Use this skill before or during drafting to:
- Validate a book promise before writing too much prose.
- Escape the author's curse of knowledge.
- Find the strongest reader profile and use case.
- Test a takeaway-first TOC by teaching from it.
- Turn conversations into scope, structure, examples, and beta-reader leads.
Reference Routing
| Need |
Read |
| Core model and terminology |
references/core/knowledge.md |
| Interview and synthesis rules |
references/core/rules.md |
| Example prompts and synthesis patterns |
references/core/examples.md |
| Fast setup and review checklist |
references/core/checklist.md |
| Run a conversation round |
workflows/run-reader-conversations.md |
Workflow
1. Define The Learning Goal
Choose one primary question for this round:
- Is the reader problem real and urgent?
- Which reader profile cares most?
- What does the reader already know or believe?
- Which promise is easiest to understand and recommend?
- Does the TOC sequence help the reader receive value?
Do not mix early listening with pitching unless the user is explicitly running a teaching conversation.
2. Recruit Readers Who Match The Hypothesis
Start with friendly first contacts, existing readers, community members, customers, students, or people already trying to solve the problem.
Avoid cold outreach unless no warm path exists. If nobody relevant will talk, treat that as a scope or access problem rather than a scheduling problem.
3. Run The Right Conversation Type
Use two modes:
- Listening conversation: explore lived experience, language, urgency, alternatives, and obstacles.
- Teaching conversation: help the reader through one slice of the TOC and watch where they get value, confusion, skepticism, or missing steps.
4. Synthesize Into Book Decisions
After each batch, update:
- Reader profile and exclusions.
- Promise wording and reader language.
- TOC order, section titles, and missing steps.
- Proof, examples, objections, and caveats.
- Potential beta readers, testimonials, or launch allies.
5. Decide The Next Test
Recommend one of:
- More listening with a sharper reader segment.
- Teaching a high-value chapter or section.
- Revising the TOC with
book-toc-lab.
- Drafting enough for
reader-experience-edit or beta-reader-feedback.
Output Format
When helping with reader conversations, return:
- Learning goal and target reader hypothesis.
- Recruiting list or outreach plan.
- Conversation guide with prompts.
- Note-taking schema.
- Synthesis table: signal, evidence, implication, book decision.
- Next test or manuscript action.
Quality Bar
Keep the conversation about the reader's life before the author's idea. Prefer observed behavior, concrete stories, and exact reader language over opinions, compliments, or predictions.
Source: hashgraph-online/awesome-codex-plugins → plugins/LVTD-LLC/skills/skills/book-reader-conversations/SKILL.md
1---2name: book-reader-conversations3description: Plan and synthesize pre-draft reader conversations for useful nonfiction books, including listening interviews, teaching calls, reader-language capture, promise validation, scope refinement, and TOC testing. Use when validating a practical book idea, finding target readers, preparing interview prompts, testing a table of contents, or turning reader conversations into book decisions.4---567# Book Reader Conversations89## Core Lens1011Reader conversations are product discovery for useful nonfiction. The goal is not to ask whether people like a book idea. The goal is to understand the reader's real situation, language, failed attempts, urgency, objections, and ability to receive the value the book intends to deliver.1213Use this skill before or during drafting to:1415- Validate a book promise before writing too much prose.16- Escape the author's curse of knowledge.17- Find the strongest reader profile and use case.18- Test a takeaway-first TOC by teaching from it.19- Turn conversations into scope, structure, examples, and beta-reader leads.2021## Reference Routing2223| Need | Read |24|------|------|25| Core model and terminology | `references/core/knowledge.md` |26| Interview and synthesis rules | `references/core/rules.md` |27| Example prompts and synthesis patterns | `references/core/examples.md` |28| Fast setup and review checklist | `references/core/checklist.md` |29| Run a conversation round | `workflows/run-reader-conversations.md` |3031## Workflow3233### 1. Define The Learning Goal3435Choose one primary question for this round:3637- Is the reader problem real and urgent?38- Which reader profile cares most?39- What does the reader already know or believe?40- Which promise is easiest to understand and recommend?41- Does the TOC sequence help the reader receive value?4243Do not mix early listening with pitching unless the user is explicitly running a teaching conversation.4445### 2. Recruit Readers Who Match The Hypothesis4647Start with friendly first contacts, existing readers, community members, customers, students, or people already trying to solve the problem.4849Avoid cold outreach unless no warm path exists. If nobody relevant will talk, treat that as a scope or access problem rather than a scheduling problem.5051### 3. Run The Right Conversation Type5253Use two modes:5455- **Listening conversation**: explore lived experience, language, urgency, alternatives, and obstacles.56- **Teaching conversation**: help the reader through one slice of the TOC and watch where they get value, confusion, skepticism, or missing steps.5758### 4. Synthesize Into Book Decisions5960After each batch, update:6162- Reader profile and exclusions.63- Promise wording and reader language.64- TOC order, section titles, and missing steps.65- Proof, examples, objections, and caveats.66- Potential beta readers, testimonials, or launch allies.6768### 5. Decide The Next Test6970Recommend one of:7172- More listening with a sharper reader segment.73- Teaching a high-value chapter or section.74- Revising the TOC with `book-toc-lab`.75- Drafting enough for `reader-experience-edit` or `beta-reader-feedback`.7677## Output Format7879When helping with reader conversations, return:80811. Learning goal and target reader hypothesis.822. Recruiting list or outreach plan.833. Conversation guide with prompts.844. Note-taking schema.855. Synthesis table: signal, evidence, implication, book decision.866. Next test or manuscript action.8788## Quality Bar8990Keep the conversation about the reader's life before the author's idea. Prefer observed behavior, concrete stories, and exact reader language over opinions, compliments, or predictions.9192---9394**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/LVTD-LLC/skills/skills/book-reader-conversations/SKILL.md`
hashgraph-online