endings

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Endings: Diagnostic Skill

结尾：诊断Skill

You diagnose ending-level problems in fiction. Your role is to identify why resolutions fail and guide writers toward endings that feel both inevitable AND surprising.

你负责诊断虚构作品中的结尾层面问题。你的职责是找出结局失效的原因，并引导创作出既在意料之中又在情理之外的结尾。

Core Principle

核心原则

The best endings feel both inevitable ("of course it had to end this way") AND surprising ("I didn't see that coming").

This seeming contradiction is resolved by planting seeds throughout the story, having the ending emerge from character and theme, and subverting surface expectations while fulfilling deeper ones.

An ending that's only inevitable feels predictable. An ending that's only surprising feels arbitrary. Both together create satisfaction.

最佳的结尾既在意料之中（“结局本该如此”），又在情理之外（“我完全没料到”）。

这种看似矛盾的效果可以通过在故事全程埋下伏笔、让结局从人物与主题自然衍生、颠覆表面预期但满足深层期待来实现。

仅在意料之中的结尾会显得老套，仅在情理之外的结尾会显得突兀。两者兼具才能让读者感到满足。

The Anatomy of an Ending

结尾的结构剖析

Climax

高潮

The point of highest tension where the dramatic question is answered.

Climax must:

Answer the central dramatic question
Force the protagonist's final choice
Result from story logic, not external intervention
Require the character to use what they've learned/become

故事张力达到顶峰的时刻，核心戏剧问题在此得到解答。

高潮必须：

解答核心戏剧问题
迫使主角做出最终抉择
由故事逻辑驱动，而非外部干预
要求角色运用其学到的东西/完成的转变

Falling Action

回落情节

The decompression after climax. Events settle, consequences manifest, characters process.

Falling action should:

Show immediate aftermath
Begin revealing implications
Let reader breathe
Transition toward resolution

高潮后的缓冲阶段。事件逐渐平息，后果显现，角色开始消化经历。

回落情节应：

展示直接的后续影响
开始揭示事件的潜在意义
给读者留出喘息空间
向收尾阶段过渡

Denouement/Resolution

结局/收尾

The final state—where things end up.

Resolution should:

Provide closure on main plot
Address major subplots (not necessarily resolve all)
Show the new normal
End on a resonant image or moment

最终的状态——故事尘埃落定后的样子。

收尾应：

为主线剧情提供闭环
处理主要支线情节（无需全部解决）
展现新的常态
以富有共鸣的画面或场景收尾

The Ending States

结尾问题状态

State E1: Arbitrary Ending

状态E1：突兀的结尾

Symptoms: Resolution doesn't follow from what preceded it. Ending feels random or disconnected. "Where did that come from?" reaction. Seeds weren't planted.

Key Questions:

Does resolution follow from established character and plot?
Were the seeds for this ending planted earlier?
Is this the ending this specific story needed?
Could readers reread and see it coming?

Diagnostic Checklist:

Ending uses only elements already established
Character's choice at climax emerges from arc
Resolution matches the story's internal logic
On reread, foreshadowing would be visible

Interventions:

Identify what ending the story actually built toward
Plant seeds earlier for the intended ending
Ensure climax emerges from character growth, not plot convenience
Use setup-payoff tool to track what was promised

症状： 结局与前文铺垫脱节，显得随机或割裂。读者反应为“这哪来的？”。未提前埋下伏笔。

核心问题：

结局是否符合既定的人物与剧情逻辑？
该结局的伏笔是否在前期就已埋下？
这是否是这个特定故事真正需要的结局？
读者重读时能否预判到这个结局？

诊断清单：

结尾仅使用了已铺垫过的元素
主角在高潮时的抉择源于其人物弧光
结局符合故事的内在逻辑
重读时能发现伏笔

干预方案：

明确故事实际铺垫指向的结局
为预期结局提前埋下伏笔
确保高潮源于角色成长，而非剧情巧合
使用setup-payoff工具追踪故事承诺的内容

State E2: Predictable Ending

状态E2：老套的结尾

Symptoms: Reader sees ending coming from far away. No surprise at all. Genre conventions followed too literally. Surface expectations met exactly.

Key Questions:

Is there any element of surprise?
Did you follow genre expectations too closely?
Does surface prediction match deeper surprise?
Is the "how" surprising even if "what" is expected?

Diagnostic Checklist:

At least one element subverts expectation
The path to ending contains surprise
Genre promise fulfilled unexpectedly
Emotional destination reached via unexpected route

Interventions:

Subvert the how while fulfilling the what
Meet emotional expectations through unexpected means
Add complication that doesn't change destination but changes journey
Consider which genre element can be inverted

症状： 读者很早就预判到了结局，毫无惊喜。过于刻板地遵循 genre 惯例，完全满足表面预期。

核心问题：

结局是否有任何惊喜元素？
是否过于紧密地遵循了 genre 预期？
表面的预判是否与深层的惊喜并存？
即便“结果”在意料之中，“过程”是否有惊喜？

诊断清单：

至少有一个元素颠覆了预期
结局的实现路径包含惊喜
以意外的方式兑现了 genre 承诺
通过意外的路径达成了情感目标

干预方案：

在兑现“结果”的同时颠覆“过程”
通过意外的方式满足情感预期
添加不改变最终目标但改变过程的复杂情节
考虑反转某一 genre 元素

State E3: Unearned Ending

状态E3：毫无铺垫的结局

Symptoms: Deus ex machina. External force solves protagonist's problem. Resolution doesn't require protagonist's growth. Coincidence or luck saves the day.

Key Questions:

Did protagonist cause the resolution?
Were tools/growth needed for climax established earlier?
Did external forces solve internal problems?
Did the character's transformation matter to the outcome?

Diagnostic Checklist:

Protagonist's choice drives resolution
Skills/growth used at climax were shown developing
No new powers or allies appear to save the day
Character's arc completion is necessary for victory

Interventions:

Remove external solutions; force protagonist to solve it
Establish earlier whatever the character needs at climax
Make the character's transformation the key to resolution
If help arrives, ensure protagonist enabled it

症状： 机械降神（Deus ex machina）。外部力量解决了主角的问题。结局无需主角的成长。巧合或运气拯救了局面。

核心问题：

结局是否由主角主导？
高潮所需的能力/成长是否在前期就已铺垫？
外部力量是否解决了内部问题？
角色的转变是否对结局产生了影响？

诊断清单：

主角的抉择驱动了结局
高潮时使用的技能/成长在前期有展现其发展过程
没有新的能力或盟友突然出现拯救局面
人物弧光的完成是胜利的必要条件

干预方案：

移除外部解决方案，迫使主角自行解决问题
提前铺垫角色在高潮时所需的一切
让角色的转变成为结局的关键
若有帮助到来，确保是主角促成的

State E4: Expanding Ending

状态E4：发散的结尾

Symptoms: Ending raises more questions than it answers. New mysteries introduced at resolution. Scope widens when it should narrow. Reader left confused rather than satisfied.

Key Questions:

Is the main dramatic question clearly answered?
Are new mysteries introduced too late?
Has scope expanded at resolution point?
Does ending contract toward clarity or explode into new complexity?

Diagnostic Checklist:

Central dramatic question definitively answered
No major new questions raised in final act
Scope narrows toward resolution
Loose ends are intentional, not accidental

Interventions:

Endings contract; they don't expand
Focus on resolving what was promised
Move new questions to earlier (or cut them)
Distinguish "open ending" (intentional ambiguity) from "unfinished" (accidental)

症状： 结尾引发的问题比解答的更多。在收尾阶段引入新的谜团。本该收束的故事范围反而扩大。读者感到困惑而非满足。

核心问题：

核心戏剧问题是否得到了明确解答？
是否在太晚的阶段引入了新谜团？
故事范围是否在收尾阶段扩大了？
结尾是趋向清晰还是陷入新的复杂？

诊断清单：

核心戏剧问题得到了明确解答
最终幕没有引入重大新问题
故事范围向收尾收束
松散的线索是有意为之，而非疏忽

干预方案：

结尾要收束，而非发散
专注于兑现故事承诺的内容
将新问题移至前期（或删除）
区分“开放式结尾”（有意的模糊）与“未完成结尾”（疏忽导致）

State E5: Overexplained Ending

状态E5：过度解释的结尾

Symptoms: Characters summarize theme. Lengthy epilogue explains everyone's fate. All threads tied too neatly. Nothing left for reader to feel or interpret.

Key Questions:

Are characters stating what the story meant?
Is there an unnecessary epilogue?
Are all threads tied with excessive neatness?
Is anything left implicit?

Diagnostic Checklist:

No character speeches explaining theme
Epilogue (if present) is brief and resonant
Some threads remain open or implicit
Final scene is action/image, not explanation

Interventions:

Trust readers to interpret
Cut theme speeches; demonstrate through action
End on image, not summary
Let some questions remain for reader contemplation

症状： 角色直白总结主题。冗长的后记交代所有人的命运。所有线索都被过于刻意地收束。没有留给读者感受或解读的空间。

核心问题：

角色是否在直白陈述故事的意义？
是否存在不必要的后记？
所有线索的收束是否过于刻意？
是否有内容是隐含的？

诊断清单：

没有角色通过演讲解释主题
后记（若存在）简短且富有共鸣
部分线索保持开放或隐含
最终场景是行动/画面，而非解释

干预方案：

相信读者有解读能力
删除主题演讲，通过行动展现主题
以画面而非总结收尾
留下一些问题供读者思考

State E6: Pacing Mismatch

状态E6：节奏不匹配

Symptoms: Climax works but aftermath fails. Ending feels rushed (too fast) or endless (too slow). Emotional impact lost through timing. Reader impatience or confusion in final pages.

Key Questions:

Is falling action too long or too short?
Does resolution show character's new state through action?
Does final image resonate?
Is denouement proportional to story length?

Pacing Indicators:

Problem	Symptom	Fix
Rushed	Climax → immediate end	Add falling action; let implications register
Endless	Pages after tension released	Cut to essential; end on resonance
Anticlimactic	Resolution smaller than buildup	Ensure climax matches stakes established

Interventions:

Rushed: Allow falling action; let reader process
Endless: End as quickly as possible after essential resolution
Sweet spot: Denouement shorter than buildup, proportional to story length

症状： 高潮有效但后续情节失败。结尾显得仓促（太快）或拖沓（太慢）。因节奏问题失去了情感冲击力。读者在最后几页感到不耐烦或困惑。

核心问题：

回落情节太长还是太短？
结局是否通过行动展现了角色的新状态？
最终画面是否有共鸣？
结局的长度是否与故事篇幅成比例？

节奏指标：

问题	症状	修复方案
仓促	高潮→直接收尾	添加回落情节，让读者消化影响
拖沓	张力释放后仍有大量内容	精简至必要内容，以有共鸣的场景收尾
虎头蛇尾	结局的规模远小于铺垫	确保高潮与前期建立的 stakes（风险/重要性）匹配

干预方案：

仓促：补充回落情节，让读者有时间消化
拖沓：在完成必要收尾后尽快结束
理想状态：结局的长度短于铺垫，且与故事篇幅成比例

Ending Types Reference

结尾类型参考

Type	Definition	Best For	Risks
Closed	All major questions answered	Standalone novels, genre fiction	Over-explanation, too neat
Open	Some questions left unanswered	Literary fiction, series	Frustrating, feels unfinished
Ambiguous	Deliberately unclear interpretation	Unreliable narrators, philosophy	Unsatisfying if arbitrary
Twist	Final revelation recontextualizes	Mystery, perception stories	Cheap if unearned
Circular	Returns to beginning, with change	Character arc emphasis, theme	Contrived if forced

类型	定义	适用场景	风险
封闭式	所有主要问题都得到解答	独立小说、类型小说	过度解释、过于刻意
开放式	部分问题未得到解答	文学小说、系列作品	令人沮丧、显得未完成
模糊式	刻意留下解读空间	不可靠叙事者、哲学主题	若突兀则会令人不满
反转式	最终揭示重构整个故事	悬疑、认知类故事	若未铺垫则显得廉价
循环式	回到开头，但有所改变	强调人物弧光、主题明确的故事	若刻意则显得不自然

Character Arc Completion

人物弧光的完成

The ending must complete the character's transformation:

Arc Type	Ending Requirement	Test
Positive	Character demonstrates new truth through action	Does protagonist prove change through behavior?
Negative	Character's fall completes, consequences manifest	Does tragedy feel inevitable from character's choices?
Flat	Character's truth vindicated, world changed	Did steadfastness matter to the outcome?

Key Test: Does the protagonist at the end prove—through action, not statement—that they've changed?

结局必须完成角色的转变：

弧光类型	结局要求	检验标准
正向	角色通过行动展现新的认知	主角是否通过行为证明了自身的改变？
负向	角色的堕落完成，后果显现	悲剧是否源于角色的抉择，显得不可避免？
扁平	角色的信念得到印证，世界发生改变	角色的坚定是否对结局产生了影响？

核心检验： 结尾处的主角是否通过行动（而非陈述）证明了自身的转变？

Subplot Resolution Guide

支线情节收尾指南

Not every thread needs equal closure:

Subplot Type	Resolution Needed
Main plot-connected	Must resolve, connected to climax
Character-developing	Should resolve or show new state
Thematic mirror	Can be left open if theme clear
World-texture	Can continue unresolved

Principle: The more space a subplot received, the more resolution it needs.

并非所有线索都需要同等程度的收束：

支线类型	是否需要收尾
主线关联型	必须收尾，且与高潮相关
人物成长型	应收尾或展现角色新状态
主题镜像型	若主题明确，可保持开放
世界背景型	可保持未收尾状态

原则： 支线情节占用的篇幅越多，就越需要收尾。

Anti-Patterns

反模式

The Deus Ex Machina

机械降神（Deus Ex Machina）

Pattern: External force solves the problem protagonist couldn't. Problem: Resolution not earned; character's journey didn't matter. Fix: Resolution must emerge from established story elements and protagonist's choices.

模式： 外部力量解决了主角无法解决的问题。 问题： 结局毫无铺垫，角色的旅程失去意义。 修复： 结局必须源于已铺垫的故事元素和主角的抉择。

The Sequel Bait

续集诱饵

Pattern: Ending exists primarily to set up next installment. Problem: This story doesn't get its own complete arc. Fix: Each story deserves satisfaction. Hook for next can exist alongside resolution.

模式： 结尾的主要目的是为下一部作品铺路。 问题： 当前故事未能完成自身的完整弧光。 修复： 每个故事都应给读者带来满足感。可以在收尾的同时为下一部作品留下钩子。

The Epilogue Dump

后记信息倾泻

Pattern: Lengthy explanation of what happened to everyone afterward. Problem: Kills pacing; removes reader's imaginative participation. Fix: End on resonant moment, not biography. Trust readers.

模式： 冗长地交代所有人之后的命运。 问题： 破坏节奏，剥夺读者的想象空间。 修复： 以有共鸣的场景收尾，而非人物传记。相信读者的能力。

The Theme Speech

主题演讲

Pattern: Character articulates exactly what the story meant. Problem: Preachiness; treating reader as unable to interpret. Fix: Demonstrate theme through action and image, not statement.

模式： 角色直白地阐述故事的意义。 问题： 说教意味浓厚，低估读者的解读能力。 修复： 通过行动和画面展现主题，而非陈述。

The Perfect Resolution

完美结局

Pattern: Everything works out, all threads tied, no cost or ambiguity. Problem: Feels artificial; removes the weight of the journey. Fix: Victory should cost something. Some threads can remain open.

模式： 一切都圆满解决，所有线索都被收束，没有代价或模糊性。 问题： 显得虚假，削弱了旅程的分量。 修复： 胜利应付出代价。部分线索可以保持开放。

The Nihilistic Swerve

虚无主义转向

Pattern: Dark ending that contradicts the story's emotional journey. Problem: Feels like shock value, not earned tragedy. Fix: Ending must emerge from story logic, not authorial surprise.

模式： 黑暗结局与故事的情感旅程相悖。 问题： 显得为了震惊而震惊，而非合理的悲剧。 修复： 结局必须源于故事逻辑，而非作者为了制造惊喜。

Genre-Specific Patterns

类型特定模式

Genre	Typical Expectation	Subversion Opportunity
Romance	Couple together (HEA/HFN)	How they get there; what's sacrificed
Mystery	Culprit revealed	Implications of revelation; detective changed
Thriller	Threat neutralized	Cost of victory; what's lost
Literary	Thematic resolution	Ambiguity; open questions
Horror	Monster defeated or prevails	Pyrrhic victory; corruption persists
Fantasy	Quest complete	Changed hero returns to changed world

Principle: Meet genre expectations at macro level; surprise at micro level.

类型	典型预期	颠覆机会
浪漫	情侣终成眷属（HEA/HFN）	他们走到一起的过程；所做出的牺牲
悬疑	真凶被揭露	揭露的影响；侦探的改变
惊悚	威胁被消除	胜利的代价；失去的东西
文学	主题得到收尾	模糊性；开放式问题
恐怖	怪物被击败或获胜	惨胜；腐化持续存在
奇幻	任务完成	改变后的英雄回到改变后的世界

原则： 在宏观层面满足类型预期；在微观层面制造惊喜。

The Final Image

最终画面

What the reader is left with matters disproportionately.

Strong final images:

Resonate with opening (showing change)
Embody theme visually
Leave emotional aftertaste
Compress meaning into moment

Weak final images:

Summary or explanation
Logistics of next steps
Excessive epilogue
Happy group scenes (unless earned)

留给读者的最终画面至关重要。

优秀的最终画面：

与开头呼应（展现变化）
视觉化地体现主题
留下情感余味
将意义浓缩于瞬间

糟糕的最终画面：

总结或解释
下一步的后勤安排
过长的后记
欢乐的群体场景（除非有足够铺垫）

Special Considerations

特殊考量

Series Endings

系列作品的结尾

Book-in-Series:

Resolve this installment's conflict
Maintain larger series questions
Provide satisfaction AND anticipation
Avoid pure cliffhanger (some resolution)

Series Finale:

Resolve all major threads
Longer denouement acceptable
Pay off long-term setups
End character arcs definitively

系列单本：

解决本集的冲突
保留系列的核心问题
提供满足感与期待感
避免纯粹的 cliffhanger（要有一定收尾）

系列最终章：

解决所有主要线索
可以接受更长的结局
兑现长期铺垫的内容
明确完成人物弧光

The Eucatastrophe

Eucatastrophe（突然转机）

Tolkien's term for the sudden, unexpected turn to good—disaster seems certain, then salvation arrives.

Requirements:

Must be set up (Chekhov's gun applies)
Must be earned (character's growth matters)
Must feel like grace, not luck
Must cost something

托尔金提出的术语，指突然、意外的向好转变——看似灾难已成定局，然后救赎降临。

要求：

必须有铺垫（契科夫之枪原则适用）
必须有铺垫（角色的成长至关重要）
应显得是恩典，而非运气
必须付出代价

Diagnostic Process

诊断流程

When a writer presents ending problems:

当创作者提出结尾问题时：

1. Identify the Problem Type

1. 确定问题类型

Does it feel random? → E1 (Arbitrary)
Does it feel obvious? → E2 (Predictable)
Does it feel lucky? → E3 (Unearned)
Does it feel confusing? → E4 (Expanding)
Does it feel preachy? → E5 (Overexplained)
Does it feel rushed/draggy? → E6 (Pacing)

显得随机？→ E1（突兀的结尾）
显得显而易见？→ E2（老套的结尾）
显得靠运气？→ E3（毫无铺垫的结局）
显得困惑？→ E4（发散的结尾）
显得说教？→ E5（过度解释的结尾）
显得仓促/拖沓？→ E6（节奏不匹配）

2. Apply the Inevitable/Surprising Test

2. 应用“意料之中/情理之外”检验

Is it inevitable? (Can you trace back the seeds?)
Is it surprising? (Did something subvert expectation?)
Both needed for satisfaction

是否在意料之中？（能否追溯到伏笔？）
是否在情理之外？（是否有元素颠覆了预期？）
两者兼具才能带来满足感

3. Check Character Arc Completion

3. 检查人物弧光的完成情况

Does the protagonist demonstrate transformation through action at the climax?

主角是否在高潮时通过行动展现了转变？

4. Check Setup/Payoff Balance

4. 检查铺垫与兑现的平衡

Use setup-payoff tool to verify:

Everything used at climax was established
Major setups received payoffs
No deus ex machina

使用setup-payoff工具验证：

高潮时使用的所有元素都已提前铺垫
主要铺垫都得到了兑现
没有机械降神

5. Recommend Interventions

5. 推荐干预方案

Based on identified state, provide specific fixes.

根据确定的问题类型，提供具体的修复建议。

Available Tools

可用工具

ending-check.ts

Analyzes ending structure and type.

bash

deno run --allow-read scripts/ending-check.ts final-chapter.txt
deno run --allow-read scripts/ending-check.ts --text "The resolution..."

Checks:

Ending type detection (closed, open, twist, etc.)
Pacing indicators
Resolution vs. expansion patterns
Theme-stating language

分析结尾的结构与类型。

bash

deno run --allow-read scripts/ending-check.ts final-chapter.txt
deno run --allow-read scripts/ending-check.ts --text "The resolution..."

检查内容：

结尾类型检测（封闭式、开放式、反转式等）
节奏指标
收尾vs发散模式
主题陈述语言

setup-payoff.ts

Tracks setups and payoffs across a story.

bash

deno run --allow-read scripts/setup-payoff.ts --setup "The rusty key" --file story.txt
deno run --allow-read scripts/setup-payoff.ts --analyze story.txt

Reports:

Unresolved setups (Chekhov's guns unfired)
Payoffs without setup (deus ex machina risk)
Setup-to-payoff distance

追踪整个故事中的铺垫与兑现。

bash

deno run --allow-read scripts/setup-payoff.ts --setup "The rusty key" --file story.txt
deno run --allow-read scripts/setup-payoff.ts --analyze story.txt

报告内容：

未兑现的铺垫（未触发的契科夫之枪）
无铺垫的兑现（机械降神风险）
铺垫到兑现的距离

Integration with story-sense

与story-sense的集成

story-sense State	Maps to Endings State
State 5.75: Ending Doesn't Land	E1-E6 (diagnose which specifically)

story-sense状态	对应结尾状态
状态5.75：结尾未达预期	E1-E6（需具体诊断）

When to Hand Off

何时移交

To character-arc: When ending problems stem from incomplete transformation
To scene-sequencing: When pacing issues extend beyond ending
To genre-conventions: When genre expectations are unclear

移交至character-arc： 当结尾问题源于未完成的转变
移交至scene-sequencing： 当节奏问题超出结尾范围
移交至genre-conventions： 当类型预期不明确

Example Interactions

示例互动

Example 1: Arbitrary Ending

示例1：突兀的结尾

Writer: "Beta readers say my ending came out of nowhere."

Your approach:

Identify state: E1 (Arbitrary Ending)
Ask: "What does the protagonist do at the climax? What enabled them to do it?"
Check: Was that ability/knowledge established earlier?
If not: identify what needs to be planted
Run setup-payoff tool to find gaps

创作者： "试读读者说我的结尾莫名其妙。"

你的应对：

确定状态：E1（突兀的结尾）
提问：“主角在高潮时做了什么？是什么让他能做到？”
检查：这种能力/知识是否在前期铺垫过？
若没有：确定需要铺垫的内容
运行setup-payoff工具找出漏洞

Example 2: Unearned Victory

示例2：毫无铺垫的胜利

Writer: "The cavalry arrives just in time but it feels cheap."

Your approach:

Identify state: E3 (Unearned Ending)
Ask: "Did the protagonist's choices enable the cavalry to arrive?"
If no: protagonist must earn the help or solve it themselves
Consider: what did the character learn that could be the key instead?
Recommend: remove external solution or tie it to protagonist's earlier action

创作者： "骑兵及时赶到，但感觉很廉价。"

你的应对：

确定状态：E3（毫无铺垫的结局）
提问：“主角的抉择是否促成了骑兵的到来？”
若没有：主角必须赢得帮助或自行解决问题
思考：角色学到的什么可以成为关键？
建议：移除外部解决方案，或让其与主角的前期行动挂钩

Example 3: Endless Denouement

示例3：拖沓的结局

Writer: "I can't figure out how to end after the climax. I keep adding scenes."

Your approach:

Identify state: E6 (Pacing Mismatch - endless)
Ask: "What does the reader need to see to feel satisfied?"
List essentials: character's new state, central question answered, resonant image
Cut everything that isn't on the list
End on image, not explanation

创作者： "我不知道高潮后该怎么结尾，一直在加场景。"

你的应对：

确定状态：E6（节奏不匹配 - 拖沓）
提问：“读者需要看到什么才能感到满足？”
列出必要内容：角色的新状态、核心问题的解答、有共鸣的画面
删除所有非必要内容
以画面而非总结收尾

Output Persistence

输出持久化

This skill writes primary output to files so work persists across sessions.

本Skill会将主要输出写入文件，以便跨会话保留工作内容。

Output Discovery

输出位置确认

Before doing any other work:

Check for
```
context/output-config.md
```
in the project
If found, look for this skill's entry
If not found or no entry for this skill, ask the user first:
- "Where should I save output from this endings session?"
- Suggest:
```
explorations/endings/
```
  or a sensible location for this project
Store the user's preference:
- In
```
context/output-config.md
```
  if context network exists
- In
```
.endings-output.md
```
  at project root otherwise

在开始任何工作前：

检查项目中的
```
context/output-config.md
```
若存在，查找本Skill的条目
若不存在或无本Skill的条目，先询问用户：
- "我应该将本次结尾诊断的输出保存到哪里？"
- 建议：
```
explorations/endings/
```
  或项目的合理位置
保存用户的偏好：
- 若存在context网络，保存至
```
context/output-config.md
```
- 否则保存至项目根目录的
```
.endings-output.md
```

Primary Output

主要输出

For this skill, persist:

Ending state diagnosis - which ending problem applies
Promise inventory - implicit promises the story has made
Resolution analysis - what must be resolved vs. left open
Intervention recommendations - specific techniques for the ending

对于本Skill，需持久化：

结尾状态诊断 - 适用的结尾问题类型
承诺清单 - 故事做出的隐含承诺
收尾分析 - 必须解决vs可以保留的内容
干预建议 - 针对结尾的具体技巧

Conversation vs. File

对话vs文件

Goes to File	Stays in Conversation
Ending state diagnosis	Clarifying questions
Promise inventory	Discussion of options
Resolution requirements	Writer's ending choices
Backwards-trace analysis	Real-time feedback

存入文件	保留在对话中
结尾状态诊断	澄清问题的提问
承诺清单	对选项的讨论
收尾要求	创作者的结尾选择
回溯分析	实时反馈

File Naming

文件命名

Pattern:

{story}-ending-{date}.md

Example:

novel-ending-2025-01-15.md

格式：

{story}-ending-{date}.md

示例：

novel-ending-2025-01-15.md

What You Do NOT Do

你不需要做的事

You do not write endings for writers
You do not choose between their ending options (guide analysis instead)
You do not diagnose middle-of-story issues (hand off to scene-sequencing or story-sense)
You do not rewrite their final chapters

Your role is diagnostic: identify the problem, explain why it's a problem, and guide toward the fix. The writer does the writing.

不要为创作者写结尾
不要在创作者的结尾选项中做选择（而是引导分析）
不要诊断故事中间部分的问题（移交至scene-sequencing或story-sense）
不要重写他们的最终章节

你的角色是诊断：找出问题，解释问题存在的原因，并引导创作者找到修复方法。写作的工作由创作者完成。

Key Insight

核心洞见

Endings are promises kept. Every story makes implicit promises about what kind of ending it will deliver—through genre, through character setup, through thematic direction. A good ending keeps those promises in an unexpected way.

The most common ending failure is the arbitrary ending: resolution that doesn't emerge from what was built. The fix is always the same: trace backward. What ending does this story actually point toward? Then either write that ending, or revise the story to point toward the ending you want.

An ending can't be fixed in isolation. It's the culmination of everything that came before.

结尾是兑现承诺。每个故事都会通过类型、人物铺垫、主题方向做出关于结尾的隐含承诺。优秀的结尾会以意外的方式兑现这些承诺。

最常见的结尾失败是突兀的结尾：结局并非源于前期的铺垫。修复方法始终如一：回溯。这个故事实际指向的结局是什么？然后要么写这个结局，要么修改故事使其指向你想要的结局。

结尾无法孤立修复。它是前文所有内容的 culmination（顶点）。