revision-continuity

Revises story chapters while auditing continuity across characters, timelines, and plot arcs.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/miyake-san/sogo-agent-platform --skill revision-continuity-miyake-san
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revision-continuity
Source: https://github.com/miyake-san/sogo-agent-platform/tree/main/skills/experimental/revision-continuity
Command: npx skills add https://github.com/miyake-san/sogo-agent-platform --skill revision-continuity-miyake-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Revising an existing story draft often introduces contradictions with earlier chapters, character states, timelines, and foreshadowing. This Skill performs targeted chapter edits and continuity audits on Story Skills projects so revisions stay consistent with the rest of the manuscript. ## Core Features & Use Cases - Continuity Audits: Detect contradictions, stale references, timeline problems, missing backlinks, and word-count drift, reported by severity with file references. - Structured Revision Passes: Supports developmental revision, line edits, and proof/polish passes with a plan that fixes what must stay constant for continuity. - Metadata Synchronization: Updates chapter frontmatter status, word counts, timelines, scene records, continuity state, and arc files after edits. - Use Case: After rewriting chapter 7 to change a character's injury, run a continuity audit to verify later chapters reflect the injury, update continuity/state.md, and revalidate the project with the story CLI. ## Quick Start Ask the assistant to run a continuity audit on chapter 7 of your story project and fix any inconsistencies it finds.

Frequently Asked Questions about revision-continuity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my novel draft for continuity errors?

Run a continuity audit that checks character knowledge, character state, timeline coherence, plot arcs, foreshadowing, promises, and world rules against your chapter files. Findings are returned ordered by severity with file references and concrete fixes.

How to revise a chapter without breaking the story timeline?

Read the target chapter plus its neighbors, timeline, and continuity state files before editing, then plan what must stay fixed. After editing, update plot/timeline.md, scene records, and continuity state, then run story validate and story doctor.

What is the difference between developmental editing and line editing?

Developmental revision improves structure, scene purpose, character motivation, pacing, stakes, and arc progression. Line editing improves clarity, voice, rhythm, dialogue, and sensory detail without changing plot facts.

Does this work if the story CLI is not installed?

Yes. If the story command is unavailable, use bun run story from the repository or the bundled story-maintenance/scripts/story.js fallback for wordcount, reindex, links, validate, and doctor maintenance.

What project structure is required before revising?

A story project must already exist with story.md in the project root, plus chapters, scenes, continuity, and plot directories. Verify the project by checking for story.md and running story report when CLI access is available.