# Story Structure 22 Step Distilled

> Analyze and develop detailed story structure using John Truby's 22-step framework to create organically connected plots with revelations that build from beginning through the middle to the end, solving the dead-middle problem. Token-optimized distilled version.

- **Type:** Skill
- **Install:** `agentstack add skill-scott2b-claude-skills-story-structure-22-step-distilled`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [scott2b](https://agentstack.voostack.com/s/scott2b)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [scott2b](https://github.com/scott2b)
- **Source:** https://github.com/scott2b/claude-skills/tree/main/story-structure-22-step-distilled

## Install

```sh
agentstack add skill-scott2b-claude-skills-story-structure-22-step-distilled
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Story Structure: Twenty-Two Steps (Distilled)

**PRIMARY DELIVERABLE: This skill creates timestamped reference documents saved to files.**

Analyze and develop story structure using John Truby's twenty-two-step framework from *The Anatomy of Story*. These steps provide a precise map of organic plot that solves the fragmented, dead middle problem.

## Critical: File Output is MANDATORY

**This skill MUST save analysis to a timestamped file.** Conversational output alone is an incomplete task.

Writers need persistent artifacts they can:
- Reference throughout the drafting process
- Update as the story evolves
- Share with collaborators
- Compare with future iterations

**Success = A dated file exists (e.g., `2025-11-11-story-name-22-steps.md`)**
**Failure = Only conversational output with no saved file**

## Purpose

Truby's twenty-two steps are the crucial structure events in an organic plot. Building on the **seven key steps**, the additional fifteen steps are found primarily in the middle where most stories fail. They help create organic plots where events are causally connected, track the hero-opponent dance fighting for the same goal, master suspense through revealing information, build revelations that increase in intensity and pace, ensure character drives plot, and achieve dramatic impact through proper sequencing.

## When to Invoke

Use for:
- Feature-length stories (novels, screenplays, long-form) needing detailed plot structure
- Fixing "dead middle" problems where second act drags or fragments
- Tracking and sequencing revelations to ensure they build properly
- Analyzing drafts to identify missing or weak structural steps
- Creating opponent plans and counterattacks that drive complex plot
- Understanding why plot feels mechanical or predictable
- Building from seven-step foundation to add necessary complexity

**Note**: For short stories/sitcoms/short films, use **story-structure-7-steps** instead. Twenty-two steps are for longer narratives needing additional structure.

## Bundled Resources

**Assets:**
- `assets/22-step-template.md` - Template for documenting 22-step structure
- `assets/revelations-sequence-template.md` - Template for tracking revelations sequence

## The Twenty-Two Steps: Core Framework

### Organic Plot Principles

**Organic plot** means:
- Actions lead to hero's character change or explain why change is impossible
- Each event is causally connected and essential
- Action is proportionate in length and pacing
- Sequence seems to come naturally from character, not imposed by author
- No part can be displaced without ruin to the whole

**Key**: Plot tracks the hero and opponents fighting for the SAME goal, masterfully managing suspense by withholding and revealing information.

### The Steps Overview

1. **Self-revelation, need, and desire (Frame)** - Planning tool combining Steps 20, 3, 5; establishes endpoint first so all steps lead there
2. **Ghost and story world** - Past event haunting hero; world expressing hero's weakness
3. **Weakness and need** - Psychological/moral flaw; what hero must overcome (detailed treatment)
4. **Inciting event** - External event causing hero to form goal ("frying pan into fire")
5. **Desire** - Specific goal extending through story (start low, build up; detailed treatment)
6. **Ally or allies** - Who helps hero; may have own desire line
7. **Opponent and/or mystery** - Who wants to prevent hero reaching goal; must want SAME goal; hidden iceberg opponent
8. **Fake-ally opponent** - Appears ally but is actually opponent
9. **First revelation and decision** - Explosive new info (about opponent); decision; changed desire and motive
10. **Plan** - Hero's strategy to overcome opponent and reach goal
11. **Opponent's plan and main counterattack** - **Critical often-missing step**: opponent's hidden strategy and attacks
12. **Drive** - Biggest plot section: series of actions, reactions to opponent info; ensure development not repetition; hero begins immoral steps
13. **Attack by ally** - Ally confronts hero's immoral actions
14. **Apparent defeat** - 2/3 to 3/4 through; hero believes they've lost (only ONE defeat)
15. **Second revelation and decision** - New info showing victory possible; hero becomes obsessed/tyrannical; moral decline
16. **Audience revelation** - Audience learns what hero doesn't; often reveals fake-ally opponent's true identity
17. **Third revelation and decision** - Hero discovers (often fake-ally truth); becomes more determined
18. **Gate, gauntlet, visit to death** - Conflict intensifies, options narrow; sudden mortality realization spurs fight
19. **Battle** - Final confrontation in smallest space; **what values are fighting**, not just who's stronger; theme explodes
20. **Self-revelation** - Hero learns who they really are; sudden, shattering, new; through action not statement (detailed treatment)
21. **Moral decision** - Hero chooses between two values/ways of living; proves self-revelation
22. **New equilibrium** - What has fundamentally changed; higher or lower level

**Note**: Steps 3, 5, and 20 appear both in Step 1 (Frame) as planning overview AND in their sequential positions with full detail.

## Task Instructions

### Step 1: Establish Output Location FIRST

**Before beginning analysis**, establish where the final document will be saved:

1. Get current date: `date +%Y-%m-%d`
2. Ask where to save structure analyses (suggest `structure/` or `process/structure/`)
3. Make note of the filename format: `YYYY-MM-DD-[story-name]-22-steps.md`

This ensures the file creation is not forgotten and sets the proper context.

### Step 2: Understand Story Context

1. Ask which story to analyze/develop
2. Search for story files if not specified (narrative drafts, outlines, structure docs, character notes)
3. Determine if:
   - New story needing detailed plot structure
   - Existing draft with middle/plot problems
   - Story in development with seven-step foundation needing expansion
   - Plot diagnosis (specific structural problem)

**Length check**: Confirm story is long enough for 22 steps. Short stories/sitcoms typically only hit seven major steps. Feature films/novels/hour-long TV usually need at least twenty-two.

### Step 3: Assess Foundation

**Seven-step check** - Are these defined?
1. Weakness and need
2. Desire
3. Opponent
4. Plan
5. Battle
6. Self-revelation
7. New equilibrium

**If undefined**: Consider using **story-structure-7-steps** skill first, then return.
**If exist**: Proceed to expand with additional fifteen steps.

### Step 4: Choose Analysis Approach

**A. Forward Development (New Story)**
- Start with frame (Step 1: self-revelation, need, desire)
- Work through steps 2-22 systematically
- Build by establishing causal connections
- Focus on organic revelations that build

**B. Reverse Engineering (Existing Draft)**
- Read/analyze existing material
- Identify which twenty-two steps present (explicit or implicit)
- Assess which missing or underdeveloped
- Map existing elements to structure
- Identify where plot weakens or fragments

**C. Plot Diagnosis (Dead Middle/Structural Problem)**
- Identify weak/missing step(s)
- Check if revelations build or stall
- Assess opponent's plan and counterattacks
- Focus on specific structural problem
- Use twenty-two steps to diagnose and solve

Ask writer which approach fits their situation.

### Step 5: Work Through the Steps

For each step, use the framework questions to develop the story structure:

**Step 1 (Frame)**: Establish self-revelation (endpoint), weakness/need, and desire (beginning) as planning overview. Ensure hero is wrong at beginning about what they'll learn at end. This frame combines Steps 20, 3, and 5 to set the structural journey.

**Step 2**: Identify ghost (past event haunting hero; open wound; counterdesire) and story world (expresses hero's weakness). Determine opening type: community start (paradise), running start (classic - ghost, slavery, weaknesses), or slow start (purposeless hero).

**Step 3**: Detail psychological weakness (flaw hurting hero), psychological need (what must overcome), moral weakness (clearly hurting others at story start), moral need (what must overcome to stop hurting others), and immediate problem (crisis at beginning).

**Step 4**: Identify inciting event - external event causing hero to form goal. Use "frying pan into fire" principle: hero thinks this solves their problem when it actually gets them into worst trouble.

**Step 5**: Establish desire - specific goal that extends through most of story. Start at low level to allow building. Show how desire intensifies and stakes increase as story progresses.

**Steps 6-8**: Define allies (with own desire lines), opponent (must want SAME goal; necessary opponent who attacks hero's weakness; iceberg hierarchy technique), fake-ally opponent.

**Step 9**: First explosive revelation (about opponent); decision; changed desire and motive.

**Steps 10-11**: Hero's plan; **opponent's plan and hidden counterattacks** (crucial often-missing step - the more intricate and hidden, the better the plot).

**Steps 12-13**: Drive (development not repetition; hero's action changes fundamentally; begins immoral steps); attack by ally (confronts hero's immorality).

**Step 14**: Apparent defeat (only ONE; explosive, devastating).

**Steps 15-17**: Second revelation (obsessive drive, moral decline); audience revelation (knows before hero; distance); third revelation (more determined despite opposition).

**Step 18**: Gate/gauntlet/visit to death (intensify conflict, narrow options; mortality realization spurs fight).

**Step 19**: Battle (smallest space; values fighting; theme explodes; hero most like opponent yet crucial differences clearer).

**Steps 20-21**: Self-revelation (sudden, shattering, through action; optional double reversal); moral decision (choose between values; proves revelation; optional thematic revelation).

**Step 22**: New equilibrium (fundamental change; lasting impact).

### Step 6: Track Revelations Sequence

**Critical technique**: Separate reveals from plot and examine as one unit.

**Create revelations list**: Extract all major revelations. Target: 7-10 for average story; more for detective/thriller. (Industry standard: average hit Hollywood film has 7-10 major reveals.)

**Assess sequence:**
1. **Logical order**: Occur in order hero would most likely learn them?
2. **Build in intensity**: Each stronger (general buildup)?
3. **Increasing pace**: Get closer together as story progresses?

**Quality checks:**
- How many about opponent? (Best kind)
- Any not explosive enough?
- Do breaks in buildup cause plot to stall?
- Is there a reversal where audience's understanding changes instantly?

Offer to create revelations sequence document using `assets/revelations-sequence-template.md`.

### Step 7: Verify Organic Connections

**Connection tests:**
- Frame: Self-revelation addresses weakness/need from beginning?
- Desire ↔ Opponent: Competing for SAME goal?
- Opponent ↔ Weakness: Is this necessary opponent (best able to attack hero's great weakness)?
- Revelations: Build logically and intensify?
- Drive: Develops (not repeats same beat)?
- Plot: Seems natural from character rather than author-imposed?

**Causality**: Are all events causally connected? Is each essential?

Identify weak connections and suggest strengthening.

### Step 8: Provide Analysis and Recommendations

**For new stories:**
- Which steps well-defined? Which need development (especially middle)?
- What to work on first?
- Missing connections?
- Opponent's plan detailed enough?

**For existing drafts:**
- Which steps present and working? Which missing/underdeveloped?
- Where does plot fragment or drag (dead middle)?
- How to strengthen weak steps?
- Do revelations build or stall?

**For plot diagnosis:**
- Which step is problem source?
- How to fix it?
- What ripple effects?
- Is middle missing opponent plan/counterattack?

### Step 9: Save Structure Documentation (REQUIRED)

**MANDATORY: Do not consider the task complete until file is saved.**

1. Create directory if needed using Bash (e.g., `mkdir -p structure`)
2. Use Write tool to save file with the filename established in Step 1: `YYYY-MM-DD-[story-name]-22-steps.md`
3. Use structure format from `assets/22-step-template.md`
4. Include complete step-by-step breakdown and assessment/recommendations from Steps 5-8
5. Offer to create revelations sequence doc: `YYYY-MM-DD-[story-name]-revelations-sequence.md`
6. Confirm save location to user with full file path

**Validation Checklist - Before Completing:**
- [ ] Date obtained via Bash in Step 1
- [ ] Save location confirmed with user in Step 1
- [ ] Analysis completed in Steps 2-8
- [ ] File written using Write tool
- [ ] File path confirmed to user
- [ ] Revelations sequence document offered

**If any checkbox is unchecked, the task is incomplete.**

## Critical Reminders

- **Build from seven steps**: Twenty-two expands the seven. Ensure seven-step foundation solid first.
- **Flexibility in order**: Steps represent general order humans solve life problems, but every story differs. Beware drastic reordering (risks fake/contrived story).
- **Revelations key**: Plot quality comes down to revelation quality. Target 7-10 major reveals; ensure they build.
- **Opponent's plan crucial**: Most writers miss Step 11. More intricate and hidden = better plot.
- **Development not repetition**: During drive, hero's action changes fundamentally—don't hit same beat.
- **Same goal**: Opponent must want SAME goal as hero (not just oppose hero).
- **Show, don't tell**: Self-revelation through action, not statement.
- **Organic not mechanical**: Plot must seem natural from character, not author-imposed.
- **Solve dead middle**: Additional fifteen steps (beyond seven) map through difficult middle section.

## What This Skill Does NOT Do

- Replace writer's creative vision or storytelling instincts
- Guarantee "good" story (execution matters)
- Work for short stories (use seven-step skill)
- Provide scene-by-scene dialogue or prose (establishes structural foundation)
- Eliminate need for other story elements (character depth, world-building, theme, symbol)
- Work as mechanical formula (must adapt to unique story)

## Integration with Other Skills

- **story-structure-7-steps** - Foundation; twenty-two expands it
- **symbol-web** - Symbols deepen steps with thematic resonance
- **narrative-inventory** - Catalogues draft; twenty-two shows if structure present
- **narrative-keywords** - Identifies themes; twenty-two ensures they build toward self-revelation
- **narrative-maps** - Shows spatial structure; twenty-two shows dramatic structure

---

*Based on John Truby's "Twenty-Two-Step Story Structure" from The Anatomy of Story*

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [scott2b](https://github.com/scott2b)
- **Source:** [scott2b/claude-skills](https://github.com/scott2b/claude-skills)
- **License:** Apache-2.0

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-scott2b-claude-skills-story-structure-22-step-distilled
- Seller: https://agentstack.voostack.com/s/scott2b
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.