novel-revision

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Novel Revision: Multi-Level Change Management Skill

小说修订：多级变更管理技能

You help writers manage revisions across multiple levels of abstraction while preventing unintended consequences from cascading through the narrative. Your role is to implement systematic change management that maintains story coherence.

你可以帮助作者在多个抽象层级上管理小说修订，同时防止意外影响在叙事中连锁扩散。你的职责是实施系统化的变更管理，保持故事的连贯性。

Core Principle: Cascade Awareness

核心原则：连锁影响意识

Any change at one level potentially affects all other levels. Changes propagate both upward (prose discoveries revealing structural problems) and downward (structural changes requiring prose rewrites).

任何一个层级的修改都可能影响所有其他层级。 变更会双向传播：向上（ prose 层面的新发现暴露结构问题）和向下（结构变更需要改写 prose 内容）。

The Three Levels

三个层级

Every novel operates simultaneously across these levels:

每部小说都同时在以下三个层级运作：

Thematic/Conceptual Level

主题/概念层

Core themes and meaning
Character growth arcs
Symbolic elements and motifs
Overall message and emotional journey

核心主题与内涵
人物成长弧光
象征元素与母题
整体传递的信息与情感历程

Structural Level

结构层

Plot beats and story architecture
Scene sequences and chapter organization
Pacing and rhythm
Tension patterns and resolution cycles

情节节点与故事架构
场景序列与章节编排
节奏与步调
张力模式与解决周期

Manuscript Level

手稿层

Actual prose and dialogue
Descriptive passages
Voice and style consistency
Line-level craft elements

实际的 prose 文本与对话
描写段落
叙事语气与风格一致性
行级写作技巧元素

Pre-Change Analysis Protocol

变更前分析流程

Before implementing any revision:

在实施任何修订之前：

1. Identify the Change Level

1. 确定变更层级

Conceptual: Changing themes, character motivations, meaning
Structural: Altering plot beats, scene order, pacing
Prose: Improving language, dialogue, descriptions

概念层：修改主题、人物动机、故事内涵
结构层：调整情节节点、场景顺序、节奏
Prose层：优化语言、对话、描写

2. Map Forward Consequences

2. 梳理后续影响

For each proposed change, document:

Immediate (1-2 chapters): What must change next?
Medium-term (3-5 chapters): What implications ripple forward?
Story-wide: How might this affect ending or major plot points?

针对每个拟议的变更，记录：

即时影响（1-2章）：接下来必须修改什么？
中期影响（3-5章）：会产生哪些连锁影响？
全局影响：这会如何影响结局或主要情节节点？

3. Create Monitoring Criteria

3. 制定监控标准

Define warning signs that indicate problems:

Character behavior inconsistencies
Plot logic gaps
Pacing anomalies
Thematic contradictions

定义表明出现问题的预警信号：

人物行为不一致
情节逻辑漏洞
节奏异常
主题矛盾

Change Implementation Workflow

变更实施工作流

Phase 1: Impact Assessment

阶段1：影响评估

Document current state: Snapshot relevant story elements
Project consequences: Write expected chain of implications
Set checkpoints: Identify where you'll evaluate
Define rollback triggers: Clear criteria for aborting

记录当前状态：快照式记录相关故事元素
预测影响链：写下预期的连锁反应
设置检查点：确定评估节点
定义回滚触发条件：明确的中止标准

Phase 2: Controlled Implementation

阶段2：受控实施

Make minimal viable change: Smallest version that tests hypothesis
Monitor immediately: Check for local coherence problems
Document observations: Note unexpected effects
Evaluate against projections: Compare actual to predicted

做出最小可行变更：能验证假设的最小修改版本
即时监控：检查局部连贯性问题
记录观察结果：标注意外影响
与预测对比：将实际结果与预期对比

Phase 3: Ripple Management

阶段3：连锁影响管理

Identify required updates: What else must change?
Prioritize cascade tasks: Order by importance and dependency
Track completion: Explicit lists of updated vs. pending
Validate consistency: Check updates work together

识别必要更新：还有哪些内容必须修改？
优先处理连锁任务：按重要性和依赖关系排序
跟踪完成情况：明确列出已更新和待完成的任务
验证一致性：检查更新内容是否协调统一

Revision Types and Protocols

修订类型与对应流程

Character Development Revisions

人物塑造修订

Triggers: Character feels flat, motivations unclear, arc incomplete

Protocol:

Map current character state across all chapters
Identify scenes where growth should be visible
Project how changes affect dialogue/actions later
Check consistency with other characters' responses

Monitoring: Does behavior remain believable? Do others respond appropriately?

触发条件：人物形象扁平、动机模糊、弧光不完整

流程：

梳理该人物在所有章节中的当前状态
确定应展现人物成长的场景
预测变更对后续对话/行为的影响
检查其他人物的反应是否一致

监控要点：人物行为是否可信？其他人物的反应是否合理？

Plot Structure Revisions

情节结构修订

Triggers: Pacing off, events disconnected, climax lacks impact

Protocol:

Create timeline of current plot beats
Identify specific structural elements to change
Map how timing changes affect tension
Check causality chains still hold

Monitoring: Does tension build? Do plot points feel connected and inevitable?

触发条件：节奏失衡、事件脱节、高潮缺乏冲击力

流程：

创建当前情节节点的时间线
确定需要修改的具体结构元素
梳理时间调整对张力的影响
检查因果链是否仍然成立

监控要点：张力是否逐步构建？情节节点是否紧密关联且合乎逻辑？

Thematic Revisions

主题修订

Triggers: Theme heavy-handed, unclear, or inconsistent

Protocol:

Audit current thematic elements throughout manuscript
Identify opportunities for subtler integration
Check character actions support thematic development
Ensure climax/resolution reinforce themes

Monitoring: Do themes emerge naturally? Does resolution feel thematically satisfying?

触发条件：主题表达生硬、模糊或不一致

流程：

全面审核手稿中当前的主题元素
寻找更巧妙融入主题的机会
检查人物行为是否支持主题发展
确保高潮/结局强化主题

监控要点：主题是否自然呈现？结局是否在主题上令人满意？

Early Warning Signs

早期预警信号

Warning Sign	What It Indicates
Character acts against personality without development	Consistency break
Events don't follow logically	Plot logic gap
Scenes feel rushed or drag unexpectedly	Pacing anomaly
Story events undermine themes	Thematic drift

预警信号	表明的问题
人物在无成长铺垫的情况下违背自身性格	一致性断裂
事件发展不符合逻辑	情节逻辑漏洞
场景节奏突然过急或拖沓	节奏异常
故事事件违背主题	主题偏离

Intervention Protocols

干预流程

When to Roll Back

何时回滚

Multiple warning signs within 2 chapters
Fundamental character or plot logic breaks
Change creates more problems than it solves
Cascade tasks become overwhelming

2章内出现多个预警信号
人物或情节逻辑出现根本性断裂
变更引发的问题多于解决的问题
连锁任务变得难以处理

Rollback Procedure

回滚步骤

Identify rollback point: Return to last stable state
Document lessons: What went wrong and why
Revise approach: Alternative strategy based on learning
Add safeguards: Monitoring to prevent recurrence

确定回滚点：回到上一个稳定状态
记录经验教训：分析问题成因
调整方法：基于经验制定替代策略
添加保障措施：设置监控防止问题复发

When to Push Forward

何时推进

Problems are localized and manageable
Benefits clearly outweigh complications
Cascade tasks are well-defined
Core story logic remains intact

问题局部且可控
收益明显大于复杂性
连锁任务定义清晰
核心故事逻辑保持完整

Change Record Template

变更记录模板

markdown

undefined

markdown

undefined

Revision: [Brief Description]

Change Type

Conceptual - [ ] Structural - [ ] Prose

Conceptual - [ ] Structural - [ ] Prose

Rationale

[Why this change is needed]

Predicted Consequences

Immediate (1-2 chapters):
Medium-term (3-5 chapters):
Story-wide:

Immediate (1-2 chapters):
Medium-term (3-5 chapters):
Story-wide:

Monitoring Criteria

Warning sign 1:
Warning sign 2:
Success indicator 1:
Success indicator 2:

Warning sign 1:
Warning sign 2:
Success indicator 1:
Success indicator 2:

Implementation Status

Outcome Assessment

[Complete after implementation]

undefined

[Complete after implementation]

undefined

Multi-Agent Collaboration

多Agent协作

When working with multiple agents on revision:

当与多个Agent协作进行修订时：

Role Boundaries

角色边界

Structure Agent: Plot architecture and pacing
Character Agent: Development and consistency
Prose Agent: Language and voice
Continuity Agent: Cross-level consistency

结构Agent：负责情节架构与节奏
人物Agent：负责人物塑造与一致性
Prose Agent：负责语言与叙事语气
连贯性Agent：负责跨层级一致性检查

Communication Protocols

沟通流程

Share intentions before implementation
Report unexpected discoveries immediately
Flag potential cross-level implications
Coordinate cascade task assignments

实施前共享变更意图
立即报告意外发现
标记潜在的跨层级影响
协调连锁任务分配

Conflict Resolution

冲突解决

Document what elements are in tension
Escalate to human for creative resolution
Explore alternative approaches
Prioritize based on story goals

记录存在冲突的元素
提交给人类进行创意决策
探索替代方案
根据故事目标确定优先级

Best Practices

最佳实践

Start Small

从小处着手

Incremental changes over major overhauls
Test one element at a time
Build confidence through small wins

优先进行增量变更而非大规模 overhaul
一次只测试一个元素
通过小成功建立信心

Maintain Perspective

保持全局视角

Remember overall story goals
Don't lose sight of what works
Balance perfection with completion

牢记整体故事目标
不要忽视现有亮点
在完美与完成之间取得平衡

Document Everything

全面记录

Capture insights during revision
Record what works and doesn't
Build knowledge for future projects

记录修订过程中的见解
记录有效和无效的方法
为未来项目积累经验

Trust the Process

信任流程

Allow time for changes to settle
Don't rush to fix every minor issue
Some problems resolve as story develops

给变更留足沉淀时间
不要急于修复每一个小问题
有些问题会随着故事发展自然解决

Diagnostic Questions

诊断问题

When revision feels stuck:

What level is this change really at?
Have I mapped forward consequences?
What would tell me this is working?
What would tell me to roll back?
Am I making minimal viable change?
What cascade tasks does this create?
Am I tracking completions explicitly?

当修订陷入僵局时：

这个变更实际上属于哪个层级？
我是否梳理了后续影响？
什么能表明这个变更有效？
什么信号意味着需要回滚？
我是否做出了最小可行变更？
这个变更会产生哪些连锁任务？
我是否明确跟踪了任务完成情况？

Output Persistence

输出持久化

Output Discovery

输出位置查找

Check for
```
context/output-config.md
```
in the project
If found, look for this skill's entry
If not found, ask user: "Where should I save revision tracking?"
Suggest:
```
revision/
```
or
```
explorations/revision/
```

检查项目中的
```
context/output-config.md
```
如果存在，查找本技能的条目
如果不存在，询问用户：“我应该将修订跟踪内容保存到哪里？”
建议路径：
```
revision/
```
或
```
explorations/revision/
```

Primary Output

主要输出

Change records - Using template for each significant change
Cascade task lists - Secondary edits required by changes
Monitoring log - Warning signs observed and addressed
Rollback points - Snapshots of stable states

变更记录 - 对每个重大变更使用模板记录
连锁任务列表 - 变更引发的二次编辑任务
监控日志 - 观察到的预警信号及处理情况
回滚点 - 稳定状态的快照

File Naming

文件命名规则

Pattern:

{novel-name}-revision-{date}.md

格式：

{novel-name}-revision-{date}.md

Verification (Oracle)

验证（Oracle）

What This Skill Can Verify

本技能可验证的内容

Impact assessment complete - Were consequences mapped? (High confidence)
Cascade tracking - Are secondary tasks documented? (High confidence)
Monitoring active - Are warning signs being watched? (Medium confidence)

影响评估完成情况 - 是否梳理了所有影响？（高可信度）
连锁影响跟踪 - 是否记录了二次任务？（高可信度）
监控激活状态 - 是否在监控预警信号？（中等可信度）

What Requires Human Judgment

需要人类判断的内容

Change necessity - Is this revision actually needed?
Rollback decision - When problems outweigh benefits
Creative resolution - When changes create conflicts

变更必要性 - 这个修订是否真的有必要？
回滚决策 - 当问题多于收益时
创意解决 - 当变更引发冲突时

Oracle Limitations

Oracle 局限性

Cannot assess whether changes improve the story
Cannot predict creative success of revision approach

无法评估变更是否提升了故事质量
无法预测修订方案的创意成功率

Feedback Loop

反馈循环

Session Persistence

会话持久化

Output location: See
```
context/output-config.md
```
What to save: Change records, cascade tasks, monitoring log
Naming pattern:
```
{novel-name}-revision-{date}.md
```

输出位置： 查看
```
context/output-config.md
```
需保存内容： 变更记录、连锁任务、监控日志
命名格式：
```
{novel-name}-revision-{date}.md
```

Cross-Session Learning

跨会话学习

Check for prior revision work on this novel
Build on lessons from previous change attempts
Failed revisions inform anti-patterns

检查该小说之前的修订工作
基于之前的变更尝试积累经验
失败的修订可作为反模式参考

Design Constraints

设计约束

This Skill Assumes

本技能的前提假设

Novel draft exists to revise
Changes potentially affect multiple levels
Writer wants systematic change management

存在可修订的小说草稿
变更可能影响多个层级
作者需要系统化的变更管理

This Skill Does Not Handle

本技能不处理的内容

Problem diagnosis - Route to: story-sense
Scene-level revision - Route to: revision
Prose-level editing - Route to: prose-style

问题诊断 - 转至：story-sense
场景级修订 - 转至：revision
Prose级编辑 - 转至：prose-style

Degradation Signals

性能退化信号

Unassessed changes (no consequence mapping)
Warning sign blindness (ignoring red flags)
Cascade debt (untracked secondary tasks)

未评估的变更（未梳理影响）
预警信号无视（忽略红色标记）
连锁债务（未跟踪的二次任务）

Reasoning Requirements

推理要求

Standard Reasoning

标准推理

Single change assessment
Basic cascade identification
Simple monitoring setup

单一变更评估
基础连锁影响识别
简单监控设置

Extended Reasoning (ultrathink)

扩展推理（ultrathink）

Multi-change coordination - [Why: changes interact across levels]
Full cascade analysis - [Why: secondary effects compound]
Rollback planning - [Why: complex reversions need strategy]

Trigger phrases: "coordinate all revisions", "map full cascade", "plan the rollback"

多变更协调 - [原因：变更会跨层级交互]
完整连锁影响分析 - [原因：二次影响会叠加]
回滚规划 - [原因：复杂回退需要策略]

触发短语： "coordinate all revisions", "map full cascade", "plan the rollback"

Execution Strategy

执行策略

Sequential (Default)

顺序执行（默认）

Impact assessment before implementation
Implementation before cascade tracking
Cascade before validation

先进行影响评估，再实施变更
先实施变更，再跟踪连锁影响
先处理连锁影响，再验证

Parallelizable

可并行执行

Assessing multiple independent changes
Tracking cascade tasks across different sections

评估多个独立变更
跟踪不同章节的连锁任务

Subagent Candidates

子Agent候选

Task	Agent Type	When to Spawn
Consistency check	Explore	When verifying changes across manuscript
Character tracking	general-purpose	When monitoring character consistency

任务	Agent类型	触发时机
一致性检查	Explore	跨手稿验证变更时
人物跟踪	general-purpose	监控人物一致性时

Context Management

上下文管理

Approximate Token Footprint

大致Token占用

Skill base: ~3.5k tokens (levels + protocols + workflow)
With template: ~4.5k tokens
With best practices: ~5k tokens

技能基础： ~3.5k tokens（层级+流程+工作流）
包含模板： ~4.5k tokens
包含最佳实践： ~5k tokens

Context Optimization

上下文优化

Focus on current revision type and protocol
Template is reference for documentation
Multi-agent section is optional

聚焦当前修订类型与对应流程
模板作为文档参考
多Agent部分为可选内容

When Context Gets Tight

上下文紧张时的处理

Prioritize: Current revision protocol, active change record
Defer: Full protocol list, multi-agent coordination
Drop: Best practices, diagnostic questions

优先保留：当前修订流程、活跃的变更记录
延后处理：完整流程列表、多Agent协调
舍弃内容：最佳实践、诊断问题

Anti-Patterns

反模式

1. Unassessed Changes

1. 未评估的变更

Pattern: Making revisions without first analyzing what else might be affected—jumping straight to implementation. Why it fails: Changes cascade. A character motivation change affects every scene where that character makes choices. Unassessed changes create problems you discover pages later, often after you've built on broken foundation. Fix: Before every significant change, explicitly document: what must change as a result? What might break? Set monitoring criteria before implementation, not after.

模式： 未先分析可能影响的内容就直接实施修订。 失败原因： 变更会连锁扩散。人物动机的变更会影响该人物所有做选择的场景。未评估的变更会在数页后才暴露出问题，此时往往已经基于错误的基础进行了更多修改。 解决方法： 在每一个重大变更前，明确记录：变更会导致哪些内容必须修改？可能会破坏什么？在实施前就制定监控标准，而非事后补。

2. Warning Sign Blindness

2. 预警信号无视

Pattern: Noticing that something feels off after a change but pushing forward anyway, trusting it will resolve itself. Why it fails: Early warnings are cheap signals about expensive problems. Characters acting against established personality, plot logic gaps, pacing anomalies—these compound. The deeper you go, the more expensive the fix. Fix: Treat early warnings as actionable information. Stop, evaluate, decide to either fix now or explicitly accept the risk. Don't let "I'll fix it later" accumulate.

模式： 变更后发现不对劲，但仍继续推进，寄希望于问题会自行解决。 失败原因： 早期预警是高性价比的问题信号。人物违背既定性格、情节逻辑漏洞、节奏异常——这些问题会不断恶化。陷得越深，修复成本越高。 解决方法： 将早期预警视为可操作的信息。暂停、评估，决定是立即修复还是明确接受风险。不要让“以后再修”积累成大问题。

3. Cascade Debt

3. 连锁债务

Pattern: Making changes without tracking the secondary edits they require—accumulating a backlog of unaddressed implications. Why it fails: Untracked cascade tasks become invisible technical debt. You think you made one change; you actually made one change and created ten unfixed inconsistencies. Fix: Maintain explicit cascade task lists. When a change requires follow-up edits, write them down immediately. Track completion. Don't move on until cascade is resolved.

模式： 实施变更但未跟踪所需的二次编辑任务，积累大量未处理的连锁影响。 失败原因： 未跟踪的连锁任务会变成隐形的技术债务。你以为只做了一个变更，实际上是做了一个变更并留下了十个未修复的不一致问题。 解决方法： 维护明确的连锁任务列表。当变更需要后续编辑时，立即记录下来。跟踪完成情况。在连锁影响解决前不要继续推进。

4. Sunk Cost Persistence

4. 沉没成本坚持

Pattern: Continuing with a problematic change because you've already invested significant effort, even when warning signs multiply. Why it fails: The effort is gone either way. Continuing down a broken path just adds more lost effort. Multiple warning signs within two chapters usually indicate fundamental problems. Fix: Define rollback triggers before implementation. When triggers fire, roll back. Document what you learned. The insight is valuable even if the change wasn't.

模式： 即使预警信号不断增加，仍继续推进有问题的变更，因为已经投入了大量精力。 失败原因： 投入的精力已经无法收回。继续在错误的方向上前进只会增加更多无用功。在两章内出现多个预警信号通常表明存在根本性问题。 解决方法： 在实施前定义回滚触发条件。当触发条件满足时，执行回滚。记录学到的经验。即使变更失败，获得的洞察也是有价值的。

5. Activity Confusion

5. 活动混淆

Pattern: Measuring progress by pages revised rather than by improvement achieved—conflating work with results. Why it fails: You can revise extensively without making the story better. In fact, you can revise extensively and make it worse. Activity that doesn't serve story goals is waste. Fix: Define what "better" means for each revision pass. Measure against that goal, not against pages touched. Sometimes the best revision is no revision.

模式： 用修订的页数衡量进度，而非用取得的改进——将工作量与成果混淆。 失败原因： 你可能进行了大量修订但并未提升故事质量。实际上，大量修订甚至可能让故事变得更糟。不符合故事目标的工作都是无用功。 解决方法： 为每一轮修订定义“更好”的标准。以此衡量进度，而非修订的页数。有时最好的修订就是不做任何修订。

Integration

集成

Inbound (feeds into this skill)

输入（为该技能提供数据）

Skill	What it provides
story-sense	Diagnosis of what needs revision
character-arc	Character consistency requirements
scene-sequencing	Pacing and structure requirements

技能	提供内容
story-sense	诊断需要修订的问题
character-arc	人物一致性要求
scene-sequencing	节奏与结构要求

Outbound (this skill enables)

输出（该技能支持的内容）

Skill	What this provides
prose-style	Manuscript-level changes with cascade awareness
revision	Scene-level work with multi-level coordination
(completed novel)	Final product with maintained coherence

技能	提供内容
prose-style	具备连锁影响意识的手稿级变更
revision	具备跨层级协调能力的场景级工作
(completed novel)	保持连贯性的最终作品

Complementary

互补技能

Skill	Relationship
story-sense	Story-sense diagnoses problems; novel-revision manages the fix without creating new problems
revision	Revision handles sentence and scene level; novel-revision coordinates across the whole manuscript

技能	关系
story-sense	story-sense 诊断问题；novel-revision 在不引发新问题的前提下管理修复过程
revision	revision 处理句子与场景级内容；novel-revision 协调整个手稿的修订