story-review
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.
SKILL.mdskills/story-review/SKILL.md
GitHubStory Review
Workflow
- Read core contract, style rules, story craft,
REVIEW_PROTOCOLS.md, canon, story state when present, and the requested prose scope. - 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.
- Diagnose only. Rank findings by consequence and cite the affected chapter, scene, or passage.
- Separate deterministic continuity findings from creative judgment.
- For developmental review, inspect causality, escalation, character choices, open questions, promises/payoffs, pacing, and ending consequence.
- For scene review, inspect objective, resistance, turn, aftermath, information flow, and causal handoff.
- For line/copy/proof work, preserve locked facts and meaning while narrowing the scope appropriately.
- Hand accepted findings to
revise-storyorrevise-bookrather 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.