continuity-record-skill

To track story continuity across episodes, you need a system that logs plot decisions, character state changes, and foreshadowing after each revision pass. This ensures later episodes do not contradict earlier character behavior or unresolved narrative risks.

Maintaining character consistency requires updating a persistent project memory with notes on character motivations and state changes. Reviewing this memory before writing new episodes prevents clashes in scene logic and character behavior.

Managing foreshadowing and payoff timing involves recording these narrative elements in a centralized continuity record after each writing pass. This allows you to align review-gate checkpoints and track when unresolved plot setups are scheduled to resolve.

Script review misses continuity risks when narrative decisions are not synchronized across revisions. Without capturing unresolved risks and timeline clashes in a persistent memory, later episodes easily contradict earlier setup logic and prop details.

Yes, project memory updates are designed for episode-by-episode adaptation workflows. They capture the latest plot decisions and continuity changes, ensuring cross-episode consistency is preserved throughout the serialized story revision process.

When revising a serialized story, check for clashes in names, timelines, props, motivations, and scene logic. Flagging these unresolved continuity risks early prevents them from spreading and contradicting earlier episodes.