Story review

Use this skill when the user wants diagnosis, scoring, comparison, approval, or revision advice for existing prose.

• First identify the applicable standard from genre, target audience, tone, platform, and explicit user preference. Everyday comedy, literary fiction, romance, mystery, and commercial serials should not share one logic-density threshold.
• In an active book, use the auditor for persisted chapters. Show concrete issue descriptions, severity, evidence, and likely reader impact.
• A parser or model-format failure is an audit failure, not evidence that the prose is bad and not permission to rewrite it.
• Do not revise merely because an audit failed. Revise when the user asks, or when the confirmed workflow authorizes it; report whether the revised artifact was actually applied.
• Preserve the user's voice and successful passages. Prefer the smallest scope that resolves the real defect.
• Respond in the user's language.

Load references/review-matrix.md for a full review or when standards are disputed.