revision-continuity

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

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.

在不丢失连贯性的前提下修订现有Story Skills项目。此Skill可用于针对性章节编辑、连贯性审核、发展性修订、行编辑，以及在下一章节撰写前的预检。

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.

必须已存在一个故事项目。可通过检查项目根目录下是否有

story.md

来验证，若有CLI访问权限，可运行或查看

story report .

命令。

Revision Workflow

修订工作流

Clarify the pass type unless the user already specified it:
- Continuity audit - find contradictions, stale references, timeline problems, missing backlinks, or word-count drift
- Developmental revision - improve structure, scene purpose, character motivation, pacing, stakes, and arc progression
- Line edit - improve clarity, voice, rhythm, dialogue, and sensory specificity without changing plot facts
- Proof/polish - fix small wording, grammar, repetition, and formatting issues
Read the relevant context:
- ```
story.md
```
- ```
chapters/_index.md
```
- The target chapter(s)
- Previous and next chapters when present
- Relevant character, location, system, and arc files referenced by the chapter frontmatter
- Matching scene files in
```
scenes/
```
- ```
continuity/state.md
```
  , open questions, and promises/payoffs
- ```
plot/timeline.md
```
  and active arc files for continuity-sensitive edits
Create a concise revision plan:
- What will change
- What must stay fixed for continuity
- Which files may need updates beyond the chapter
Make targeted edits directly in markdown files. Do not create project-local scripts to rewrite prose.
Update dependent metadata:
- Chapter frontmatter
```
status
```
  (
```
draft
```
  ->
```
revised
```
  ,
```
revised
```
  ->
```
final
```
  only when appropriate)
- Chapter
```
word-count
```
  via CLI when available
- ```
plot/timeline.md
```
  if events changed
- ```
scenes/
```
  records if POV, location, participants, or state changes moved
- ```
continuity/state.md
```
  ,
```
continuity/questions/
```
  , or
```
continuity/promises/
```
  when knowledge, object ownership, mystery state, or payoffs changed
- Arc plot points or foreshadowing status if the revision changes setup/payoff
- Character or location files when state, relationship, or location references changed
Run maintenance:

shell

story wordcount . --write
story reindex .
story links .
story validate .
story continuity .
story doctor .

story continuity

deterministically checks death ordering (

died-in

vs later appearances), promise/question chapter ordering, unfired setups, POV/cast consistency, and

continuity/state.md

references. For intentional flashbacks, memories, or recordings of dead characters, list them under chapter or scene

mentions

instead of

characters

story

is not installed, use

bun run story --

from this repository or the bundled

story-maintenance/scripts/story.js

fallback when available.

明确修订类型，除非用户已指定：
- 连贯性审核 - 查找矛盾、过时引用、时间线问题、缺失反向链接或字数偏差
- 发展性修订 - 改进结构、场景目的、角色动机、节奏、冲突和弧光推进
- 行编辑 - 在不改变剧情事实的前提下，提升清晰度、语气、节奏、对话和感官细节
- 校对/润色 - 修正措辞、语法、重复和格式方面的小问题
阅读相关上下文：
- ```
story.md
```
- ```
chapters/_index.md
```
- 目标章节
- 若存在，查看前后章节
- 章节前置元数据引用的相关角色、地点、设定和弧光文件
- ```
scenes/
```
  中的对应场景文件
- ```
continuity/state.md
```
  、未解决问题以及伏笔/回收内容
- 对连贯性敏感的编辑需参考
```
plot/timeline.md
```
  和活跃弧光文件
创建简洁的修订计划：
- 将要修改的内容
- 为保证连贯性必须保留的内容
- 除章节外可能需要更新的文件
直接在markdown文件中进行针对性编辑。请勿创建项目本地脚本重写散文内容。
更新依赖元数据：
- 章节前置元数据
```
status
```
  （仅在合适时从
```
draft
```
  改为
```
revised
```
  ，从
```
revised
```
  改为
```
final
```
  ）
- 若有CLI权限，更新章节
```
word-count
```
- 若事件有变化，更新
```
plot/timeline.md
```
- 若视角、地点、参与者或状态变化有调整，更新
```
scenes/
```
  记录
- 若知识、物品所有权、谜团状态或伏笔回收有变化，更新
```
continuity/state.md
```
  、
```
continuity/questions/
```
  或
```
continuity/promises/
```
- 若修订改变了伏笔/回收，更新弧光剧情点或伏笔状态
- 若状态、关系或地点引用有变化，更新角色或地点文件
运行维护命令：

shell

story wordcount . --write
story reindex .
story links .
story validate .
story continuity .
story doctor .

story continuity

会确定性检查死亡顺序（

died-in

与后续出场）、伏笔/问题的章节顺序、未回收的伏笔、视角/角色一致性以及

continuity/state.md

引用。对于有意设置的闪回、回忆或死者的记录内容，请将其列在章节或场景的

mentions

下，而非

characters

中。

若未安装

story

，可从本仓库运行

bun run story --

，或在可用时使用捆绑的

story-maintenance/scripts/story.js

作为备选方案。

Continuity Audit Checklist

连贯性审核清单

Run

story continuity .

first to collect the deterministic findings, then check for what the CLI cannot judge:

Character knowledge: no one acts on information they have not learned
Character state: injuries, emotions, alliances, location, and status carry forward
Timeline: time of day, travel time, sequence, and cause/effect stay coherent
Plot arcs: each changed scene still advances or intentionally pauses an arc
Foreshadowing: planted and paid-off items match arc files
Promises/questions: durable continuity records match what the chapter now reveals or withholds
Scene state: every chapter scene has machine-readable POV, location, participants, arcs, and state-change notes
World rules: magic, technology, politics, and geography stay consistent with worldbuilding files
References: chapter frontmatter lists every major character, location, and arc advanced in the prose
Registries: indexes, word counts, and links are current after edits

先运行

story continuity .

收集确定性检查结果，再检查CLI无法判断的内容：

角色认知：无人会基于未获知的信息采取行动
角色状态：伤势、情绪、联盟、地点和状态需保持连贯
时间线：时间、行程时长、事件顺序和因果关系需一致
剧情弧光：每个修改后的场景仍需推进或有意暂停一条弧光
伏笔：埋下的线索和回收的内容需与弧光文件匹配
伏笔/问题：持久的连贯性记录需与章节当前揭示或隐藏的内容一致
场景状态：每个章节场景需具备机器可读的视角、地点、参与者、弧光和状态变化说明
世界观规则：魔法、科技、政治和地理需与世界观构建文件保持一致
引用：章节前置元数据需列出散文中涉及的所有主要角色、地点和推进的弧光
注册表：编辑后索引、字数和链接需保持最新

Reporting

报告

When the user asks for an audit rather than direct edits, return findings ordered by severity with file references and concrete fixes. When the user asks for revision, summarize the edited files, changed continuity facts, and maintenance results.

当用户要求审核而非直接编辑时，按严重程度排序返回检查结果，并附上文件引用和具体修复方案。当用户要求修订时，总结编辑的文件、修改的连贯性事实以及维护结果。