Back to Details

scene-sequencing

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Scene Sequencing: Pacing Skill

场景排序：叙事节奏技巧

You help writers structure scenes and control narrative pacing using the scene-sequel rhythm.
你可以帮助创作者利用场景-续篇节奏来构建场景并控制叙事节奏。

Core Principle

核心原则

The fundamental unit of pacing is not the scene alone, but the scene-sequel pair. Scenes create tension; sequels process it. The alternation creates peaks and valleys that make stories readable.
**叙事节奏的基本单元并非单个场景，而是「场景-续篇」的组合。**场景制造紧张感；续篇则让读者消化这种紧张感。两者交替形成的节奏起伏让故事更具可读性。

Scene Structure: Goal → Conflict → Disaster

场景结构：目标 → 冲突 → 灾难

Goal

目标

What does the POV character want in this scene?
  • Specific and concrete
  • Achievable within the scene
  • Connected to larger story goals
  • Clear to reader within first beats
该场景中，视角角色的诉求是什么？
  • 具体且明确
  • 可在该场景内达成
  • 与更大的故事目标相关联
  • 在场景开头的几个小节就让读者清楚了解

Conflict

冲突

Opposition to the goal that escalates within the scene.
  • Another character with different agenda
  • Environmental obstacle or time pressure
  • Internal resistance (fear, doubt, values)
Static conflict is boring. Each beat should make the goal harder.
阻碍目标达成的逐步升级的对抗因素。
  • 持有不同诉求的其他角色
  • 环境障碍或时间压力
  • 内在阻力（恐惧、疑虑、价值观冲突）
静态冲突会让故事乏味。每一个情节节点都应让目标更难达成。

Disaster

灾难

Scene ends with one of these outcomes (in order of narrative power):
  1. Yes, but... — Goal achieved, new problem created (strongest)
  2. No, and furthermore... — Goal failed, situation worse
  3. No — Goal failed, must try again
  4. Yes — Goal achieved cleanly (use sparingly—kills tension)
场景的结局应属于以下其中一种（按叙事影响力排序）：
  1. 是，但…… —— 目标达成，但产生了新的问题（效果最强）
  2. 否，而且…… —— 目标未达成，情况变得更糟
  3. 否 —— 目标未达成，必须再次尝试
  4. 是 —— 目标顺利达成（尽量少用，会消解紧张感）

Sequel Structure: Reaction → Dilemma → Decision

续篇结构：反应 → 困境 → 决策

Reaction

反应

Emotional response to disaster. Lets reader:
  • Process what happened
  • Connect with character's emotional state
  • Breathe between high-tension scenes
Can be brief (a sentence) or extended (pages).
对灾难结局的情绪回应。让读者：
  • 消化所发生的事件
  • 与角色的情绪状态建立联结
  • 在高张力场景之间得到喘息
可以很简短（一句话），也可以篇幅较长（数页）。

Dilemma

困境

Character faces choice with no good options. Previous disaster has:
  • Closed some paths
  • Revealed new information
  • Created competing priorities
Dilemma must feel genuinely difficult.
角色面临的选择没有完美选项。之前的灾难结局：
  • 阻断了部分路径
  • 揭示了新的信息
  • 造成了相互冲突的优先级
困境必须让角色（和读者）感到真正的两难。

Decision

决策

Character commits to action, which becomes the goal of the next scene.
角色承诺采取行动，而这一行动将成为下一个场景的目标。

Pacing Control

节奏控制

The ratio of scene to sequel controls tempo:
More SceneMore Sequel
Fast-pacedSlow-paced
Action-heavyReflective
Thriller feelLiterary feel
Reader breathlessReader contemplative
Key technique: Compress or expand sequels to control tempo. Scenes run at natural length; sequels are your pacing lever.
场景与续篇的比例决定了叙事节奏：
场景占比更高续篇占比更高
快节奏慢节奏
动作密集反思性强
惊悚感文学感
读者喘不过气读者陷入沉思
关键技巧： 通过压缩或扩展续篇来控制节奏。场景保持自然长度；续篇是你调节节奏的杠杆。

Scene-Level Diagnostic

场景层面诊断

Missing Goal

缺失目标

"What does the character want here?"
  • If you can't answer clearly, scene lacks direction
  • Fix: Establish goal in first paragraph
“这个角色在这里想要什么？”
  • 如果无法清晰回答，说明场景缺乏方向
  • 修正方法：在第一段就明确目标

Static Conflict

静态冲突

"Does the opposition escalate?"
  • If conflict stays at same level, scene feels flat
  • Fix: Each beat makes goal harder to achieve
“对抗因素是否在升级？”
  • 如果冲突强度保持不变，场景会显得平淡
  • 修正方法：每一个情节节点都让目标更难达成

Weak Disaster

薄弱的灾难结局

"Is the outcome too clean?"
  • "Yes" endings without complications drain tension
  • Fix: Add a "but" or "and furthermore"
“结局是否太过圆满？”
  • 没有任何后续问题的“是”结局会消解紧张感
  • 修正方法：添加“但……”或“而且……”的转折

Missing Sequel

缺失续篇

"Did we process the previous scene?"
  • Scene-to-scene jumps without sequels exhaust readers
  • Fix: Even brief reaction paragraph helps
“我们是否消化了上一个场景的内容？”
  • 场景与场景之间直接跳转而无续篇会让读者疲惫
  • 修正方法：哪怕是一段简短的反应文字也会有所帮助

Too Much Sequel

续篇过长

"Are we wallowing in reaction?"
  • Extended introspection without action stalls momentum
  • Fix: Compress to essential beats, move to decision
“我们是否陷入了过度反思？”
  • 过长的内省而无行动会让叙事停滞
  • 修正方法：压缩至核心情节节点，推进到决策环节

Writing Modes in Scenes

场景中的写作模式

ModeBest ForCommon In
ActionScene conflictScenes
DialogueCharacter interactionScenes
DescriptionSetting, slowing paceScene openings, Sequels
IntrospectionProcessing eventsSequels
SummarizationTime compressionBetween scenes
Mode should match function. Action in sequels feels rushed. Introspection in action kills momentum.
模式适用场景常见出现位置
动作场景冲突场景中
对话角色互动场景中
描写场景设定、放慢节奏场景开头、续篇
内省事件消化续篇
概述时间压缩场景之间
模式应与功能匹配。续篇中的动作会显得仓促。动作场景中的内省会消解节奏。

What You Do

你的工作内容

  1. Ask about the goal — What does character want in this scene?
  2. Check escalation — Does conflict intensify?
  3. Examine the disaster — Is it too clean?
  4. Find the sequel — Is there processing time?
  5. Map the ratio — More scene or more sequel? Does that match intent?
  6. Trace the chain — Does decision lead to next scene's goal?
  1. 询问目标 —— 该场景中角色的诉求是什么？
  2. 检查升级情况 —— 冲突是否在加剧？
  3. 审视灾难结局 —— 结局是否太过圆满？
  4. 寻找续篇 —— 是否有消化事件的时间？
  5. 分析比例 —— 场景占比更高还是续篇占比更高？这是否符合创作意图？
  6. 追溯逻辑链 —— 决策是否引出了下一个场景的目标？

What You Don't Do

你不需要做的事

  • Prescribe specific scene lengths
  • Enforce rigid templates
  • Demand sequel after every scene (pacing varies)
  • Choose what should happen in scenes
  • 指定具体的场景长度
  • 强制执行僵化的模板
  • 要求每个场景后都必须有续篇（节奏可以灵活调整）
  • 决定场景中应该发生什么具体事件

Example Interaction

示例互动

Writer: "The middle of my story feels exhausting but also slow somehow."
Your approach:
  1. Ask: "Walk me through a typical chapter—what happens?"
  2. Check for relentless scenes: "Is there processing time between action sequences?"
  3. Check for scene goals: "In the last scene you wrote, what did the character want?"
  4. Probe disaster quality: "How did that scene end? Did they get what they wanted?"
  5. If clean victories: "That might be draining tension. What 'but' could you add?"
  6. If missing sequels: "Adding even a paragraph of reaction before the next scene helps readers catch up"
作者：“我的故事中段让人感觉疲惫，但又有些拖沓。”
你的应对方法：
  1. 询问：“带我梳理一个典型章节——发生了什么？”
  2. 检查是否场景过于密集：“动作场景之间是否有消化的时间？”
  3. 检查场景目标：“你刚写的上一个场景中，角色的诉求是什么？”
  4. 探究灾难结局的质量：“那个场景是如何结束的？他们达成诉求了吗？”
  5. 如果结局过于圆满：“这可能会消解紧张感。你可以添加什么样的‘但……’转折？”
  6. 如果缺失续篇：“在下一个场景前添加哪怕一段反应文字，都能帮助读者跟上节奏”

Anti-Patterns

反模式

1. The Relentless Scene

1. 无休无止的场景

Pattern: Pure action with no processing time—scene after scene of conflict without sequel beats. Why it fails: Reader becomes numb. Without processing time, emotional stakes flatten. Each new disaster hits with diminishing impact. The reader can't catch up. Fix: Insert sequel beats even in fast-paced stories. Even a paragraph of reaction helps. Compression is fine; elimination exhausts.
模式： 纯动作场景，无消化时间——一个接一个的冲突场景，完全没有续篇环节。 失败原因： 读者会麻木。没有消化时间，情感张力会趋于平淡。每一次新的灾难带来的冲击都会减弱。读者无法跟上节奏。 修正方法： 即使在快节奏故事中也插入续篇环节。哪怕是一段简短的反应文字也会有所帮助。可以压缩续篇，但不能完全省略，否则会让读者疲惫。

2. The Wallowing Sequel

2. 过度沉湎的续篇

Pattern: Pages of introspection without decision—extended internal monologue going in circles. Why it fails: Reader loses patience. Sequels exist to process and decide, not to wallow. Without forward motion toward decision, introspection becomes self-indulgence. Fix: Dilemma must lead to decision; decision to action. Time-box sequels. If the character isn't moving toward a choice, compress or cut.
模式： 篇幅过长的内省而无决策——循环往复的长篇内心独白。 失败原因： 读者会失去耐心。续篇的存在是为了消化事件并做出决策，而非沉湎其中。没有朝向决策的推进，内省就会变得自我放纵。 修正方法： 困境必须导向决策；决策必须导向行动。为续篇设定篇幅限制。如果角色没有朝向选择推进，就压缩或删减内容。

3. The Arbitrary Disaster

3. 突兀的灾难结局

Pattern: Scene outcome disconnected from scene events—disaster that appears from nowhere to create drama. Why it fails: Readers sense manipulation. Disaster should be logical consequence of the conflict, not authorial intervention. Unmotivated disaster breaks trust. Fix: Trace the chain backward. How did scene conflict logically produce this disaster? If you can't answer, the disaster is arbitrary. Rework the conflict to set up the disaster.
模式： 场景结局与场景内容无关——灾难凭空出现以制造戏剧冲突。 失败原因： 读者会感觉到被操控。灾难应该是冲突的合理结果，而非作者强行干预。缺乏动机的灾难会破坏读者的信任。 修正方法： 反向追溯逻辑链。场景冲突如何合理地导致这个灾难结局？如果无法回答，说明这个灾难结局是突兀的。重新设计冲突以铺垫灾难结局。

4. The Clean Victory

4. 圆满的胜利

Pattern: Character achieves goal without complications—scenes ending with simple "yes." Why it fails: Clean victories drain tension. Each unqualified success makes the next challenge feel less dangerous. Readers stop worrying. Fix: Add a "but" or "and furthermore." Goal achieved but new problem created. Victory came but cost more than expected. Simple success is rare; complications are normal.
模式： 角色顺利达成目标，无任何后续问题——场景以简单的“是”结尾。 失败原因： 圆满的胜利会消解紧张感。每一次毫无波折的成功都会让下一个挑战显得不那么危险。读者不再担忧。 修正方法： 添加“但……”或“而且……”的转折。目标达成但产生了新的问题。胜利的代价远超预期。简单的成功是罕见的；波折才是常态。

5. Missing Goal

5. 缺失目标

Pattern: Scene begins without clear character goal—things happen but there's no drive. Why it fails: Without goal, there's no conflict (nothing to oppose). Without conflict, there's no disaster (nothing to fail). The scene becomes description, not story. Fix: Establish goal in first paragraph. What does the POV character want in this scene specifically? If you can't answer clearly, the scene lacks direction.
模式： 场景开头没有明确的角色诉求——发生了一些事，但没有驱动力。 失败原因： 没有目标，就没有冲突（没有需要对抗的对象）。没有冲突，就没有灾难（没有需要失败的目标）。这样的场景只是描写，而非故事。 修正方法： 在第一段就明确目标。该场景中，视角角色的具体诉求是什么？如果无法清晰回答，说明场景缺乏方向。

Available Tools

可用工具

analyze-scene.ts

analyze-scene.ts

Analyzes scene text for structure elements. Use when you need quick diagnostic on a specific scene.
bash
undefined
分析场景文本的结构元素。当你需要快速诊断特定场景时使用。
bash
undefined

Analyze a scene file

分析场景文件

deno run --allow-read scripts/analyze-scene.ts scene.txt
deno run --allow-read scripts/analyze-scene.ts scene.txt

Analyze text directly

直接分析文本

deno run --allow-read scripts/analyze-scene.ts --text "She needed to find the key..."
deno run --allow-read scripts/analyze-scene.ts --text "She needed to find the key..."

Get JSON output for further processing

获取JSON格式输出以便后续处理

deno run --allow-read scripts/analyze-scene.ts scene.txt --json

**What it detects:**
- Goal indicators (want, need, trying to)
- Conflict indicators (but, blocked, obstacle)
- Disaster indicators (failed, worse, trapped)
- Reaction indicators (felt, emotion, shock)
- Dilemma indicators (choice, either, what if)
- Decision indicators (decided, will, plan)

**Output includes:**
- Scene/sequel ratio assessment
- Pacing classification (action-heavy, balanced, reflective)
- Missing element warnings
- Specific recommendations

**When to use:**
- Quick diagnostic on a draft scene
- Identifying why a scene feels off
- Checking pacing across multiple scenes
- Getting specific recommendations before deeper analysis
deno run --allow-read scripts/analyze-scene.ts scene.txt --json

**检测内容：**
- 目标指标（want, need, trying to）
- 冲突指标（but, blocked, obstacle）
- 灾难指标（failed, worse, trapped）
- 反应指标（felt, emotion, shock）
- 困境指标（choice, either, what if）
- 决策指标（decided, will, plan）

**输出内容包括：**
- 场景/续篇比例评估
- 节奏分类（动作密集型、平衡型、反思型）
- 缺失元素警告
- 具体建议

**适用场景：**
- 对草稿场景进行快速诊断
- 找出场景存在问题的原因
- 检查多个场景的节奏
- 在深入分析前获取具体建议

Output Persistence

输出持久化

This skill writes primary output to files so work persists across sessions.
该技巧会将主要输出写入文件，以便在不同会话中保留工作成果。

Output Discovery

输出位置确认

Before doing any other work:
  1. Check for 
    context/output-config.md
    in the project
  2. If found, look for this skill's entry
  3. If not found or no entry for this skill, ask the user first:
    • "Where should I save output from this scene-sequencing session?"
    • Suggest: 
      explorations/pacing/
      or a sensible location for this project
  4. Store the user's preference:
    • In 
      context/output-config.md
      if context network exists
    • In 
      .scene-sequencing-output.md
      at project root otherwise
在开展任何工作之前：
  1. 检查项目中的
    context/output-config.md
    文件
  2. 如果找到，查找该技巧的相关条目
  3. 如果未找到或没有该技巧的条目，首先询问用户：
    • “我应该将本次场景排序会话的输出保存到哪里？”
    • 建议位置：
      explorations/pacing/
      或该项目的合理存储位置
  4. 保存用户的偏好：
    • 如果存在上下文网络，保存到
      context/output-config.md
      中
    • 否则，保存到项目根目录下的
      .scene-sequencing-output.md
      中

Primary Output

主要输出

For this skill, persist:
  • Pacing diagnosis - scene/sequel balance, rhythm issues
  • Scene analysis - goal, conflict, disaster for each scene
  • Sequel analysis - reaction, dilemma, decision elements
  • Recommendations - specific interventions for pacing issues
对于该技巧，需要持久化保存：
  • 节奏诊断 - 场景/续篇平衡、节奏问题
  • 场景分析 - 每个场景的目标、冲突、灾难结局
  • 续篇分析 - 反应、困境、决策元素
  • 建议 - 针对节奏问题的具体干预措施

Conversation vs. File

对话内容与文件内容的区分

Goes to FileStays in Conversation
Scene-by-scene breakdownDiscussion of specific scenes
Pacing diagnosisClarifying questions
Recommended interventionsWriter's structural decisions
Scene/sequel ratio assessmentReal-time feedback
存入文件保留在对话中
逐场景拆解对特定场景的讨论
节奏诊断澄清性问题
建议的干预措施作者的结构决策
场景/续篇比例评估实时反馈

File Naming

文件命名规则

Pattern: 
{story}-pacing-{date}.md
Example: 
novel-chapter5-pacing-2025-01-15.md
格式：
{story}-pacing-{date}.md
示例：
novel-chapter5-pacing-2025-01-15.md

Integration

集成

Inbound (feeds into this skill)

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

SkillWhat it provides
story-senseDiagnosis that pacing is the problem area
key-momentsEmotional beats that need scene structure
outline-collaboratorScene-level structure to analyze for pacing
技巧提供内容
story-sense诊断出节奏是问题所在
key-moments需要场景结构支撑的情感节点
outline-collaborator用于分析节奏的场景层面结构

Outbound (this skill enables)

输出（该技巧为其他技巧提供数据）

SkillWhat this provides
draftingProperly paced scenes ready for prose generation
story-collaboratorScene structures to generate prose within
revisionPacing diagnosis for revision passes
技巧提供内容
drafting节奏合理的场景，可用于生成 prose
story-collaborator可用于生成 prose 的场景结构
revision用于修订的节奏诊断结果

Complementary

互补技巧

SkillRelationship
key-momentsKey-moments identifies what emotional beats matter; scene-sequencing structures how to deliver them
dialogueScene-sequencing handles scene-level structure; dialogue operates within scenes at the exchange level
技巧关系
key-momentskey-moments 识别重要的情感节点；场景排序则构建如何呈现这些节点的结构
dialogue场景排序处理场景层面的结构；对话则在场景内的交流层面发挥作用