Summarise A Beta Reader's Notes Into A Priority List

Your beta reader sent back pages of notes, some about a plot hole, some about a misplaced comma, all mixed together with no order. This separates structural concerns from line edits, ranks the structural ones by how much of the book they touch, and gives you one list to work through. For writers facing a revision that currently feels unmanageable.

<context>
A beta reader sent detailed notes on your manuscript: {BETA_NOTES}. The notes are long, unstructured, and mix small typos with structural concerns.
</context>

<task>
**Summarise the notes into a prioritised action list:**
1. Separate structural issues (plot, pacing, character) from line-level issues (typos, word choice)
2. Rank structural issues by how much of the manuscript they touch
3. Group line-level issues into a single batch to handle in one editing pass
4. Produce a short priority list to work through in order
</task>
<output_format>
- Structural issues, ranked, each with a one-line description
- Line-level issues, grouped as one item
- A suggested order of work
</output_format>