Beta Reader Feedback
Core Lens
Beta reading is product testing for a useful nonfiction manuscript. The goal is not praise, proofreading, or opinion collection. The goal is to discover whether readers want the promise, receive the value, stay engaged, and know what to do next.
Use this skill to:
- Plan beta reader rounds.
- Recruit the right readers.
- Write reader instructions.
- Classify and synthesize comments.
- Detect hidden boredom from abandonment.
- Decide what to revise next.
- Decide when the manuscript is ready for polishing.
Reference Routing
| Need |
Read |
| Core beta-reading model and terminology |
references/core/knowledge.md |
| Operating rules and decision criteria |
references/core/rules.md |
| Example instructions, feedback classes, and synthesis patterns |
references/core/examples.md |
| Quick checklist for setup and review |
references/core/checklist.md |
| Run a beta iteration |
workflows/run-beta-iteration.md |
| Synthesize comments into revision decisions |
workflows/synthesize-feedback.md |
Workflow
1. Confirm Beta-Readiness
Start beta reading after the draft is coherent enough for motivated readers, but before it has been polished so heavily that major changes feel costly.
If the draft is still a vague TOC, use book-toc-lab. If it needs structural pacing work first, use reader-experience-edit.
2. Choose The Reader Batch
For each iteration, define:
- Target reader profile.
- Desired number of deeply engaged readers.
- Invitation list, usually larger than the desired reader count.
- Any influential readers to save for a later, stronger draft.
3. Prepare The Feedback Surface
Use a tool that supports live comments and engagement visibility.
- Prefer cloud-hosted commenting.
- Do not email PDFs around as the main workflow.
- Tell readers what feedback matters now.
- Ask for confusion, skepticism, missing information, boredom, value, and applicability.
4. Classify Feedback
Group feedback by signal:
- Evidence of value.
- Confusion or missing information.
- Skepticism or weak proof.
- Factual issues, overgeneralization, or oversimplification.
- Unnecessary drama or distracting sentences.
- Boredom, abandonment, or comment drop-off.
- Application problems after reading.
5. Revise By Signal Strength
Prioritize changes that unblock more readers.
- Treat abandonment as data.
- Treat negative feedback as a lens, not a command.
- Do not argue with readers in the document.
- Follow up when the book is supposed to change behavior after reading.
Output Format
When helping with beta feedback, return:
- Beta-readiness or setup diagnosis.
- Reader recruitment and instruction plan.
- Feedback taxonomy or synthesis table.
- Ordered revision priorities.
- Finish criteria: what evidence would make the manuscript ready for polish.
Quality Bar
Separate reader signals from author defensiveness. Do not merely summarize comments. Convert them into revision decisions, open questions, and next beta-round tests.
1---2name: beta-reader-feedback3description: Plan beta reading rounds for practical nonfiction and turn reader comments, abandonment, confusion, skepticism, and negative feedback into manuscript revisions. Use when recruiting beta readers, preparing reader instructions, synthesizing feedback, deciding whether a book is ready, or improving a draft from real reader data.4license: MIT5---67# Beta Reader Feedback89## Core Lens1011Beta reading is product testing for a useful nonfiction manuscript. The goal is not praise, proofreading, or opinion collection. The goal is to discover whether readers want the promise, receive the value, stay engaged, and know what to do next.1213Use this skill to:1415- Plan beta reader rounds.16- Recruit the right readers.17- Write reader instructions.18- Classify and synthesize comments.19- Detect hidden boredom from abandonment.20- Decide what to revise next.21- Decide when the manuscript is ready for polishing.2223## Reference Routing2425| Need | Read |26|------|------|27| Core beta-reading model and terminology | `references/core/knowledge.md` |28| Operating rules and decision criteria | `references/core/rules.md` |29| Example instructions, feedback classes, and synthesis patterns | `references/core/examples.md` |30| Quick checklist for setup and review | `references/core/checklist.md` |31| Run a beta iteration | `workflows/run-beta-iteration.md` |32| Synthesize comments into revision decisions | `workflows/synthesize-feedback.md` |3334## Workflow3536### 1. Confirm Beta-Readiness3738Start beta reading after the draft is coherent enough for motivated readers, but before it has been polished so heavily that major changes feel costly.3940If the draft is still a vague TOC, use `book-toc-lab`. If it needs structural pacing work first, use `reader-experience-edit`.4142### 2. Choose The Reader Batch4344For each iteration, define:4546- Target reader profile.47- Desired number of deeply engaged readers.48- Invitation list, usually larger than the desired reader count.49- Any influential readers to save for a later, stronger draft.5051### 3. Prepare The Feedback Surface5253Use a tool that supports live comments and engagement visibility.5455- Prefer cloud-hosted commenting.56- Do not email PDFs around as the main workflow.57- Tell readers what feedback matters now.58- Ask for confusion, skepticism, missing information, boredom, value, and applicability.5960### 4. Classify Feedback6162Group feedback by signal:6364- Evidence of value.65- Confusion or missing information.66- Skepticism or weak proof.67- Factual issues, overgeneralization, or oversimplification.68- Unnecessary drama or distracting sentences.69- Boredom, abandonment, or comment drop-off.70- Application problems after reading.7172### 5. Revise By Signal Strength7374Prioritize changes that unblock more readers.7576- Treat abandonment as data.77- Treat negative feedback as a lens, not a command.78- Do not argue with readers in the document.79- Follow up when the book is supposed to change behavior after reading.8081## Output Format8283When helping with beta feedback, return:84851. Beta-readiness or setup diagnosis.862. Reader recruitment and instruction plan.873. Feedback taxonomy or synthesis table.884. Ordered revision priorities.895. Finish criteria: what evidence would make the manuscript ready for polish.9091## Quality Bar9293Separate reader signals from author defensiveness. Do not merely summarize comments. Convert them into revision decisions, open questions, and next beta-round tests.
ConcertoNotes