revision-continuity

# Revision Continuity ## Overview Revise existing Story Skills projects without losing continuity. Use this skill for targeted chapter edits, continuity audits, developmental revision, line edits, and pre-flight checks before drafting the next chapter. ## Prerequisites A story project must already exist. Verify by checking for `story.md` in the project root, then run or inspect `story report .` when CLI access is available. ## Named Revision Passes Track a full revision as a ladder of named passes in `story.md` `revision-passes`, so the work happens in order (big structural changes before polishing sentences that may be cut) and survives between sessions: ```shell story passes . --init # writes the default ladder, keeping existing entries story passes . # checklist with the checks each pass runs story passes . --start pacing # mark a pass in-progress story passes . --done pacing # mark it done story next . # with story status revising, recommends the next unfinished pass ``` The default ladder is `structure`, `character`, `theme`, `continuity`, `pacing`, `line`, `copyedit`, `proof`. Each entry is `{pass, status}` with status `pending`, `in-progress`, or `done`; add a custom kebab-case pass (`fact-check`, `sensitivity`) with `story passes . --start <name>`, which appends it as `in-progress`. The checks per pass, as `story passes .` prints them: | Pass | Checks | Workflow below | |------|--------|----------------|...