Skip to main content
Writing & LiteratureNovel Audit240 lines

pacing-structure-collapse

Detects AI-generated pacing and structural failures in novels: uniform tension curves,

Quick Summary18 lines
Diagnoses the structural and pacing failures that AI introduces into novels — the ways a manuscript can be well-written at the sentence level but completely broken at the architecture level.

## Key Points

- Novel feels "fine but boring" despite decent prose
- Reader feedback says "nothing happens" or "I lost interest around chapter 10"
- The story feels like it's the same temperature throughout — no peaks, no valleys
- AI was used to generate large sections without a pre-planned structure
- After an outline compliance check, to assess the quality of execution beyond just hitting plot points
- Stakes (what could be lost)
- Conflict intensity (how actively forces oppose each other)
- Information revelation (how much the reader learns)
- Emotional intensity (how strongly characters feel)
- Conflicts introduced and resolved within the same chapter
- Characters who "understand" things immediately after they happen
- Arguments between characters that end with mutual understanding in the same conversation
skilldb get novel-audit-skills/pacing-structure-collapseFull skill: 240 lines
Paste into your CLAUDE.md or agent config

Pacing & Structure Collapse Detector

Diagnoses the structural and pacing failures that AI introduces into novels — the ways a manuscript can be well-written at the sentence level but completely broken at the architecture level.

When to Use This Skill

  • Novel feels "fine but boring" despite decent prose
  • Reader feedback says "nothing happens" or "I lost interest around chapter 10"
  • The story feels like it's the same temperature throughout — no peaks, no valleys
  • AI was used to generate large sections without a pre-planned structure
  • After an outline compliance check, to assess the quality of execution beyond just hitting plot points

The AI Pacing Failure Modes

Failure 1 — The Flat Line (No Tension Curve)

AI generates scenes at a consistent emotional intensity. Every scene feels roughly the same importance. There's no build, no escalation, no release.

Diagnosis method: Rate each scene on a 1-10 tension scale based on:

  • Stakes (what could be lost)
  • Conflict intensity (how actively forces oppose each other)
  • Information revelation (how much the reader learns)
  • Emotional intensity (how strongly characters feel)

Plot these ratings chapter by chapter. A healthy novel looks like a jagged upward slope with valleys. An AI novel looks like a straight horizontal line hovering around 5-6.

HEALTHY TENSION MAP:
Ch: 1  2  3  4  5  6  7  8  9  10 11 12 13 14 15 16 17 18 19 20
    3  4  5  3  6  7  4  7  8  5  6  8  9  4  7  8  9  10 6  8
    ___/\__/\___/\_____/\____/\________/\___/\______/\___/\___

AI FLAT LINE:
Ch: 1  2  3  4  5  6  7  8  9  10 11 12 13 14 15 16 17 18 19 20
    5  5  6  5  6  5  6  5  6  5  6  5  6  5  6  5  6  5  6  7
    ──────────────────────────────────────────────────────────

Failure 2 — Premature Resolution

AI resolves conflicts too quickly. A character faces a problem, and within the same scene or the next chapter, they've processed it, learned from it, and moved on. Real psychological and plot conflicts take time, create complications, and resist easy answers.

What to scan for:

  • Conflicts introduced and resolved within the same chapter
  • Characters who "understand" things immediately after they happen
  • Arguments between characters that end with mutual understanding in the same conversation
  • Mysteries or questions that are answered before tension builds
  • Villains whose plans are thwarted on the first attempt
  • Trauma processed in a single scene of reflection

The 3-beat minimum rule: Major conflicts should have at least 3 beats before resolution — introduction, complication, resolution. AI often skips the complication.

Failure 3 — The Saggy Middle

AI front-loads plot momentum (strong opening) and knows it needs a climax (strong ending) but fills the middle with:

  • Side quests that don't connect to the main plot
  • Circular conversations where characters discuss the same problem repeatedly without progress
  • Training montages and preparation scenes that delay without building
  • New characters introduced mid-book who don't serve the main arc
  • Repetitive pattern: problem → partial solution → new problem of similar scope (treadmill plot)

Middle diagnosis:

  • Does the protagonist's situation meaningfully change between the 25% mark and the 75% mark?
  • Could you remove 30% of the middle chapters without losing essential plot information?
  • Are the stakes higher at the midpoint than at the opening? (They should be.)
  • Does the protagonist make irreversible decisions in the middle? (They should.)

Failure 4 — Uniform Chapter Structure

AI defaults to a template:

THE AI CHAPTER TEMPLATE:
1. Character arrives at / wakes up in a location (200-400 words)
2. Internal reflection on recent events (300-500 words)
3. Interaction with another character (dialogue-heavy, 800-1200 words)
4. Something mildly surprising happens (200-400 words)
5. Character reflects on what it means (200-400 words)
6. Mild cliffhanger or contemplative ending (100-200 words)

Diagnosis: Extract the structural skeleton of each chapter (opening device, scene types, closing device). If more than 60% of chapters follow the same skeleton, the structure is AI-templated.

What healthy variation looks like:

  • Some chapters are one long continuous scene. Others have 3-4 scenes.
  • Some chapters open in media res. Others open with atmosphere.
  • Some chapters end on a cliffhanger. Others end on a quiet beat. One ends mid-sentence.
  • Some chapters are 1,500 words. Others are 5,000.
  • At least one chapter breaks the established pattern entirely (epistolary, flashback, different POV, time jump).

Failure 5 — Scene-to-Sequel Ratio Collapse

In narrative theory, scenes (action, conflict, decision) alternate with sequels (reaction, dilemma, decision). AI tends to collapse sequels into single paragraphs or skip them entirely, creating a breathless pace where nothing has emotional weight because nothing is processed.

Alternately, AI writes all sequel and no scene — pages of characters thinking and feeling with no external conflict happening.

Diagnosis: Label each chapter section as SCENE (external action/conflict) or SEQUEL (internal processing/reaction).

ProblemSymptom
All scene, no sequelRelentless action, emotionally hollow, reader fatigued
All sequel, no sceneNavel-gazing, nothing happens, reader bored
Scenes and sequels in rigid alternationPredictable, mechanical rhythm

Healthy pacing varies the ratio. Action sequences compress sequel. Aftermath sections expand sequel. Quiet midpoints may be extended sequel. Climax is compressed scene with sequel delayed until denouement.

Failure 6 — Escalation Failure

Each major plot event should raise the stakes higher than the last. AI often fails at this because it generates scenes independently without tracking cumulative escalation.

What to scan for:

  • Act 2 conflicts that are lower-stakes than Act 1 conflicts
  • A climax that feels like just another scene because previous scenes were equally intense
  • Multiple "dramatic" scenes in a row at the same intensity level (drama fatigue)
  • The protagonist facing essentially the same challenge repeatedly at the same difficulty level
  • Consequences that don't compound — each problem is isolated and self-contained

Escalation map:

ESCALATION AUDIT:
Scene 1: Stakes = personal embarrassment (Level 2)
Scene 5: Stakes = friendship threatened (Level 4) ✓ escalation
Scene 9: Stakes = job at risk (Level 4) ✗ FLAT — same level as scene 5
Scene 14: Stakes = relationship ending (Level 5) ✓ escalation
Scene 18: Stakes = minor misunderstanding (Level 2) ✗ COLLAPSE — below scene 1
Scene 22: Stakes = life-or-death (Level 9) ✗ JUMP — skipped levels 6-8

Failure 7 — The Clean Resolution

AI wraps everything up too neatly. Every subplot resolves. Every character gets closure. Every question is answered. Every relationship reaches equilibrium.

Real novels leave things unresolved. Some questions are answered obliquely. Some characters don't get what they wanted. Some subplots trail off because that's what happens in life.

Checklist:

  • Does every subplot resolve completely? (At least one shouldn't.)
  • Does every character end up in a clearly "good" or "bad" place? (Some should be ambiguous.)
  • Is the final chapter a tour of resolutions, checking off each plot thread? (This is AI.)
  • Does the ending answer every question raised? (It shouldn't.)
  • Could you write a single sentence describing the "moral" of the story? (If yes, it's too neat.)

Full Pacing Audit Process

Step 1: Chapter-Level Mapping

For each chapter, record:

  • Word count
  • Number of scenes
  • Opening device
  • Closing device
  • Tension rating (1-10)
  • Scene/sequel ratio
  • POV character (if multiple)
  • Time elapsed in story

Step 2: Act-Level Analysis

Divide the novel into three acts (roughly 25% / 50% / 25%) and assess:

  • Does Act 1 establish stakes and end with a point of no return?
  • Does Act 2 complicate and escalate, with a midpoint reversal?
  • Does Act 3 accelerate toward a climax that pays off Act 1's promise?

Step 3: Tension Visualization

Plot the tension map and identify:

  • The longest flat stretch (where the reader will abandon the book)
  • The highest peak before the climax (should be lower than the climax)
  • Valleys after peaks (necessary for reader recovery — but not too long)
  • The climax position (should be in the final 15-20% of the manuscript)

Step 4: Structural Recommendations

Provide specific, actionable fixes:

  • Which scenes to cut (contribute nothing to escalation)
  • Which scenes to combine (accomplish the same purpose)
  • Where to add complications (the premature resolutions)
  • Where to add rest beats (the relentless sequences)
  • Where to break the pattern (the templated chapters)

Output Format

# Pacing & Structure Audit
**Title**: [Novel title]
**Word count**: [N]

## Tension Map
[Visual tension graph by chapter]

## Structural Diagnosis
**Primary failure mode**: [which of the 7 failures is dominant]
**Chapter length variance**: [percentage — healthy is 50%+]
**Unique chapter structures**: [N of N total]
**Scene-to-sequel ratio**: [overall and per-act]
**Escalation trajectory**: [ascending / flat / erratic]

## Act Analysis
[Per-act assessment]

## Critical Fixes (Priority Order)
1. [Most impactful structural change]
2. [Second priority]
3. ...

## Scene-by-Scene Recommendations
[Specific guidance per scene: keep / cut / combine / expand / restructure]

Anti-Patterns

  • Prescribing a single "correct" structure. Not every novel follows three-act structure. Allow for experimental, literary, and non-linear forms — but even those need internal pacing logic.
  • Equating slow pacing with bad pacing. Literary fiction often has slow, deliberate pacing. The question isn't speed — it's whether each scene justifies its length with meaning, tension, or beauty.
  • Ignoring genre expectations. A thriller needs constant escalation. A literary novel needs room to breathe. A romance needs specific beat structure. Calibrate to genre.
  • Recommending cuts without understanding purpose. A "slow" chapter may provide crucial emotional grounding. Before recommending a cut, ask: what does the reader lose if this is removed?
  • Treating the outline as sacred. If the structure is broken, the outline may need changing, not just the execution.

Install this skill directly: skilldb add novel-audit-skills

Get CLI access →