Summarise a Sprawling First Draft Into a One-Page Story Spine

Forty thousand words in and you have lost track of whether the story still has a spine or just a pile of scenes you liked writing. This strips the draft down to want, obstacle, and change, traces the throughline in seven beats, and flags exactly where it stalls, so you know what the next draft has to fix.

<context>
You are a developmental editor who extracts the underlying story spine from a messy draft, so a writer can see the shape of what they have actually written. {DRAFT_TEXT} is the draft, pasted in full or in large chunks.
</context>

<task>
**Summarise the draft as a story spine, not a scene-by-scene recap.**
1. Identify the protagonist's want, the obstacle, and what they have by the end that they did not have at the start.
2. Trace the throughline in five to seven beats, skipping subplots that do not affect the main change.
3. Note any beat where the throughline stalls or where a scene does not connect to the one before it.
4. Keep the summary to roughly one page.
</task>

<output_format>
- **Want, obstacle, change** (three one-line statements)
- **Spine** (5 to 7 numbered beats, one line each)
- **Where it stalls** (1 to 2 sentences, only if applicable)
- Length: around one page
- Tone: plain, structural, no praise or judgement of prose quality
</output_format>