Diagnose and revise an existing prose story in separate structure, scene, character, continuity, and prose passes, fixing root causes before sentence polish.
Installs into .claude/skills of the current project.
Are you the author of Revise Story?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/badgids-revise-story)
---
name: revise-story
description: Diagnose and revise an existing prose story in separate structure, scene, character, continuity, and prose passes, fixing root causes before sentence polish.
disable-model-invocation: true
author: Alan Guice (Badgids)
license: Apache-2.0
---
# Revise Story
## Workflow
1. Read core contract, style rules, story craft, canon, and the complete story.
2. Diagnose before rewriting. Rank findings: structural, scene, character, continuity, prose.
3. Fix the highest-level accepted cause first.
4. Re-read affected downstream scenes after each structural change.
5. On the prose pass, remove filler, repeated meaning, generic intensifiers, fake profundity, and interchangeable dialogue.
6. Update upstream artifacts when a revision changes canon or architecture.
7. Run continuity and style checks.
8. Apply the `project-impact` procedure after accepted story changes and mark affected downstream artifacts stale.
## Done
Every accepted finding is fixed at its source level and no lower-level polish hides an unresolved structural problem.
