story-maintenance

# Story Maintenance ## Overview Run deterministic maintenance for Story Skills projects. Use the CLI for structure validation, registry rebuilds, word counts, link checks, continuity checks, project reports, next-action reports, pacing, clue, voice, and name checks, revision-pass tracking, Mermaid diagrams, schema migration, entity helpers, manuscript import, and manuscript export and builds. The creative skills still own story decisions; this skill handles mechanical consistency. ## CLI Access Prefer the first available command: 1. `story <command>` - when the package bin is installed 2. `bun run story -- <command>` - when working from this repository 3. `node scripts/story.js <command>` - bundled fallback, resolving `scripts/story.js` relative to this skill folder If none of these are available, perform the requested maintenance manually using the conventions in `story-init`. Run the installed or bundled CLI in place. Do not copy `scripts/story.js` into the user's story project, and do not create project-local build scripts, generator scripts, or bulk writer scripts to generate story content. Story projects should remain markdown-first, plus explicitly requested exports such as `dist/manuscript.md`. ## Commands Run commands from the story project root, or pass the story path explicitly. ```shell story validate . story reindex . story wordcount . --write story links . story continuity . story prose . story voices . story pacing . story clues . story timeline . stor...