feedback-triage

# Feedback Triage ## Overview Process alpha/beta reader feedback as a structured, reconcilable workflow: collect per-reader feedback files, hold all revision until the round is complete, synthesize convergent/divergent/single-reader findings into a decision record with a readiness verdict, and hand a concrete revision plan to the `revision-continuity` skill. ## Prerequisites A story project with at least one drafted chapter (or a complete draft) that readers have read. Verify `story.md` exists in the project root. ## When to Use - Starting a feedback round (recruiting readers, sending chapters out) - Recording feedback as it arrives - Synthesizing a completed round into decisions - NOT for revising the manuscript (use `revision-continuity` with the synthesis's revision plan) - NOT for the agent's own critique of the draft (use `revision-continuity` audits; reader feedback is external input) ## Workflow ### 1. Set up the round 1. Decide the round scope: which chapters readers get (`chapters-read` range) and how many readers (2–4 per round is typical; one reader is a data point, not a round). 2. Create the round folder: `feedback/round-{N}/`. 3. Give readers a review copy they can open without a terminal: ```shell story build . --format html ``` The single-file HTML copy in `dist/` has a table of contents and a stable anchor on every paragraph, shown as a clickable label beside it (`ch03-p12` is chapter 3, paragraph 12). Ask readers to cit...