Check story continuity with AI
Compare a draft with its own timeline, character knowledge and setup records, then inspect the evidence before deciding which revisions belong in the story.
To check story continuity with AI, choose the kind of inconsistency you want to find. A character may refer to a letter two chapters before learning it exists. An object might move between scenes after a rewrite removed the explanation. The revision-continuity guide connects the passage to the relevant manuscript and project records.
Structured checks can reveal contradictions where dates, facts or appearances were recorded. They cannot determine by themselves whether a change of heart feels believable. Give one revision pass a clear purpose and keep deliberate ambiguity distinct from an accidental inconsistency.
What it does
- Review continuity between selected chapters
- Check event order against the working timeline
- Trace a planted clue to its payoff
- Compare dialogue with a character’s recorded knowledge
- Update the relevant continuity record after an agreed edit
Install and use
- Install the Story Skills package and skill in a local story project. Its CLI checks need Node.js, a project definition and the relevant chapter files.
- Ask “Review chapter six only for what the protagonist knows about the letter. Cite earlier evidence and suggest corrections without editing the draft yet.”
- Read both passages before applying a correction and update the project record that owns the affected fact or clue.
FAQ
Source
Made by Daniel Dewhurst. Original skill: revision-continuity, published on GitHub under the MIT licence.
View on GitHub