endings
Diagnose weak endings, rushed resolutions, and arbitrary conclusions. Use when stories build well but end disappointingly, when climax feels unearned, or when resolution doesn't complete character arcs.
What this skill does
# 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:**
| 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
---
## 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:Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.