Endings

This is diagnostic tooling for fiction endings that fail to land. It walks you through six failure states: arbitrary (not set up), predictable (no surprise), unearned (deus ex machina), expanding (raises new questions instead of resolving), overexplained (theme speeches and endless epilogues), and pacing mismatch (rushed or dragging). Each state gets specific checklists and interventions. The core insight is solid: good endings feel both inevitable and surprising, which sounds contradictory but works when you plant seeds early and subvert surface expectations while fulfilling deeper ones. Use this when your climax works but the resolution doesn't, or when beta readers say "that's it?" The diagnostic checklists are genuinely useful for identifying which type of ending problem you have.

skills.sh installs: 461
GitHub stars: 182
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add jwynia/agent-skills --skill endings --agent claude-code

Installs into .claude/skills of the current project.

Files

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.