Maps every narrative thread in a manuscript — main plot and subplots alike — tracking where
each is introduced, developed, and resolved. Designed to catch the most common structural
failure in AI-generated novels: abandoned subplots.

## Key Points

- User says "track my subplots", "did I drop any threads", "check for loose ends"
- User wants a structural map of all narrative threads
- User suspects Chekhov's gun violations (introduced elements that never pay off)
- As a deeper dive following subplot flags from the Novel Audit's Module 3
- **The manuscript** — full text
- **Outline** (optional) — helps identify intended subplots vs. emergent ones
- Introduces a question, conflict, goal, or mystery
- Receives development across more than one scene
- Creates reader expectation of resolution
1. Assign each subplot an ID (SP-001, SP-002, ...).
2. Name it descriptively ("Marcus and Elena's rivalry", "The missing journal").
3. Classify its type (relationship, mystery, internal, external, thematic, Chekhov).

Subplot Tracker Skill

Maps every narrative thread in a manuscript — main plot and subplots alike — tracking where each is introduced, developed, and resolved. Designed to catch the most common structural failure in AI-generated novels: abandoned subplots.

When to Use This Skill

• User says "track my subplots", "did I drop any threads", "check for loose ends"
• User wants a structural map of all narrative threads
• User suspects Chekhov's gun violations (introduced elements that never pay off)
• As a deeper dive following subplot flags from the Novel Audit's Module 3

Input Requirements

• The manuscript — full text
• Outline (optional) — helps identify intended subplots vs. emergent ones

Subplot Identification

What Counts as a Subplot

A subplot is any narrative thread that:

• Introduces a question, conflict, goal, or mystery
• Receives development across more than one scene
• Creates reader expectation of resolution

Common types: relationship arcs, mystery/information threads, internal/psychological arcs, external goal threads, thematic threads, and Chekhov's elements (objects or facts introduced with implied future relevance).

One-off scene details, atmospheric worldbuilding, and recurring settings (unless the setting itself has a narrative arc) do not count as subplots.

Tracking Process

Step 1 — Thread Discovery

Read the manuscript and catalog every subplot:

1. Assign each subplot an ID (SP-001, SP-002, ...).
2. Name it descriptively ("Marcus and Elena's rivalry", "The missing journal").
3. Classify its type (relationship, mystery, internal, external, thematic, Chekhov).
4. Note the chapter and passage where it is introduced.
5. Note what reader expectation it creates.

Step 2 — Touchpoint Mapping

For each subplot, track every scene where it is advanced, referenced, or affected:

• Active touchpoint: The subplot is the primary focus of the scene
• Passive touchpoint: The subplot is referenced or briefly advanced within a scene focused on something else
• Indirect touchpoint: Events in the scene affect the subplot even though it isn't mentioned (e.g., a character death that impacts a relationship subplot)

Step 3 — Resolution Classification

Classify each subplot's ending:

Status	Definition
RESOLVED	Thread reaches a clear conclusion that satisfies the reader expectation created
PARTIALLY RESOLVED	Some aspects are concluded but questions remain
ABANDONED	Thread stops being mentioned with no resolution — reader expectation is violated
ABSORBED	Thread merges into another subplot or the main plot and is resolved there
DELIBERATELY OPEN	Thread is left open intentionally (sequel hook, thematic ambiguity)
IN PROGRESS	Manuscript is incomplete; thread is still active at the current endpoint

Step 4 — Health Assessment

Evaluate each subplot for structural health:

Gap analysis: Calculate the longest stretch (in chapters) between touchpoints. Flag if:

• A subplot disappears for more than 25% of the manuscript without resolution
• A subplot is not touched for 5+ consecutive chapters in the middle of the story

Pacing assessment: Is the subplot's development spread evenly, front-loaded, or back-loaded?

• Front-loaded subplots that fade suggest the AI lost track of them
• Back-loaded subplots that appear suddenly suggest the AI remembered them too late
• Even distribution is healthiest

Resolution quality: Does the resolution feel earned?

• Does it follow logically from the development?
• Is it given appropriate page time?
• Does it arrive at a satisfying point in the overall story structure?

Output Format

# Subplot Tracking Report
**Title**: [Novel title]
**Date**: [Today]
**Subplots identified**: [N]
**Resolved**: [N] | **Abandoned**: [N] | **Partial**: [N] | **Open**: [N]

## Subplot Map

| ID | Name | Type | Introduced | Last Touched | Status | Gap (max ch.) |
|----|------|------|-----------|-------------|--------|---------------|
| SP-001 | ... | ... | Ch. 1 | Ch. 22 | RESOLVED | 3 |
| SP-002 | ... | ... | Ch. 3 | Ch. 9 | ABANDONED | — |
| ... | ... | ... | ... | ... | ... | ... |

## Chapter-by-Chapter Thread Presence

| Chapter | Active Subplots | Introduced | Resolved | Untouched (at risk) |
|---------|----------------|------------|----------|-------------------|
| 1 | SP-001 | SP-001 | — | — |
| 2 | SP-001, SP-002 | SP-002 | — | — |
| ... | ... | ... | ... | ... |

## Detailed Thread Analysis

### SP-001: [Name]
- **Type**: [classification]
- **Introduced**: Ch. X — "[quote or description]"
- **Reader expectation**: [what the reader expects will happen]
- **Touchpoints**: Ch. X (active), Ch. Y (passive), Ch. Z (active), ...
- **Longest gap**: [N] chapters (Ch. A to Ch. B)
- **Resolution**: Ch. X — "[how it ends]"
- **Health**: [assessment]

[Repeat for each subplot]

## Critical Findings

### Abandoned Subplots
[List with impact assessment — which abandoned threads will readers notice most?]

### Chekhov's Gun Failures
[Introduced elements that never paid off]

### Overcrowded Chapters
[Chapters juggling too many active subplots, risking shallow treatment]

### Subplot Desert Chapters
[Chapters advancing no subplots at all — potential pacing dead zones]

## Recommendations
[Prioritized list of fixes, starting with abandoned subplots that readers will most notice]

Anti-Patterns

Demanding that every thread resolve. Deliberately open endings and sequel hooks are legitimate storytelling choices. Only flag threads as ABANDONED when the text gives no indication the openness is intentional.

Missing thematic subplots. Not all subplots involve characters doing things. A recurring motif (birds, mirrors, the color red) that builds thematic meaning is a thread worth tracking.

Treating every mention as a touchpoint. A character's name appearing does not mean their subplot was advanced. A touchpoint requires the subplot's central question or conflict to be meaningfully engaged.

Ignoring subplot interactions. Subplots rarely exist in isolation. When two subplots influence each other, track the interaction — it is often where the richest storytelling happens, and also where AI generation most commonly drops threads.

Recommending subplot cuts without considering theme. Before recommending a subplot be cut, consider whether it serves the theme even if it doesn't serve the plot. A subplot that seems tangential may be doing essential thematic work.