endings（endings 命令行）

Endings: Diagnostic 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

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

State E2: Predictable Ending

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

State E3: Unearned Ending

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

State E4: Expanding Ending

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

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

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:

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

Ending Types Reference

Character Arc Completion

The ending must complete the character's transformation:

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:

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

Anti-Patterns

The 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

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

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

The 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

• 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)

2. Apply the Inevitable/Surprising Test

• 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

Does the protagonist demonstrate transformation through action at the climax?

4. Check Setup/Payoff Balance

Use setup-payoff tool to verify:

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

5. Recommend Interventions

Based on identified state, provide specific fixes.

Available Tools

ending-check.ts

Analyzes ending structure and type.

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

setup-payoff.ts

Tracks setups and payoffs across a story.

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

Integration with story-sense

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

Example Interactions

Example 1: Arbitrary Ending

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

Your approach:

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

Example 2: Unearned Victory

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

Your approach:

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

Example 3: Endless Denouement

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

Your approach:

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

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 endings session?" - Suggest: explorations/endings/ or a sensible location for this project

1. Store the user's preference:

- In context/output-config.md if context network exists - In .endings-output.md at project root otherwise

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

Conversation vs. File

File Naming

Pattern: {story}-ending-{date}.md Example: 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.

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.