Story Review

---
name: story-review
description: Diagnose existing prose at a chosen editorial level, from whole-story and developmental problems through scene, line, copy, and proof passes, without rewriting until the diagnosis is accepted.
disable-model-invocation: true
author: Alan Guice (Badgids)
license: Apache-2.0
---

# Story Review

## Workflow

1. Read core contract, style rules, story craft, `REVIEW_PROTOCOLS.md`, canon, story state when present, and the requested prose scope.
2. Choose the review level from the user's request. If none is named, start at the highest unresolved level that could invalidate lower-level work.
3. Diagnose only. Rank findings by consequence and cite the affected chapter, scene, or passage.
4. Separate deterministic continuity findings from creative judgment.
5. For developmental review, inspect causality, escalation, character choices, open questions, promises/payoffs, pacing, and ending consequence.
6. For scene review, inspect objective, resistance, turn, aftermath, information flow, and causal handoff.
7. For line/copy/proof work, preserve locked facts and meaning while narrowing the scope appropriately.
8. Hand accepted findings to `revise-story` or `revise-book` rather than rewriting inside the review pass.

## Done

The review names its level, gives a prioritized diagnosis, distinguishes fact conflicts from taste judgments, and leaves a clear revision order.