---
description: Generate a structure-aware pacing report analyzing scene tempo and narrative flow.
---

# /scr:pacing-analysis -- Structure-Aware Pacing Report

Generate a pacing report that analyzes scene tempo, narrative flow, and structural rhythm.

## Usage
```
/scr:pacing-analysis [N]
```

Where `N` is the scope (act, chapter, or section number depending on work type). Omit `N` to analyze the entire manuscript.

## Instruction

You are a **pacing analyst**. Your job is to map the narrative rhythm, identify pacing problems, and ensure the story's tempo serves its structure.

---

### STEP 0: LOAD CONTEXT

1. Load `config.json` to determine work type and hierarchy
2. Load `CONSTRAINTS.json` -- this command is **hidden** from poetry and speech_song work types. If the current work type is in a hidden group, inform the writer and exit gracefully
3. Load `OUTLINE.md` -- extract structural context: which scenes are intended as climaxes, which are transitions or breathers, the overall arc shape, and any pacing notes the writer included during planning
4. Load the drafted prose for scope `N` (or full manuscript if `N` is omitted)

---

### STEP 1: SCENE LENGTH DISTRIBUTION

<scene_length_analysis>
  For each scene/chapter in scope:
  - Count word length
  - Calculate mean and median scene length
  - Identify **outliers**: scenes more than 1.5x the median (unusually long) or less than 0.5x the median (unusually short)
  - Note whether outlier length is intentional (a climax scene being longer is expected; a transition being long is suspicious)

  Present as a distribution chart:
  ```
  Ch 1  ████████████████████ 3,200w
  Ch 2  ████████████ 1,900w
  Ch 3  ████████████████████████████ 4,500w  [LONG]
  Ch 4  ████████ 1,200w
  Ch 5  ██████████████ 2,100w
  ```
</scene_length_analysis>

---

### STEP 2: TEMPO MAPPING

<tempo_classification>
  Classify each scene's dominant tempo:
  - **Action**: Physical conflict, chase, fight, urgent movement
  - **Tension**: Psychological conflict, suspense, dread, anticipation
  - **Revelation**: Discovery, plot twist, secret revealed, realization
  - **Transition**: Travel, time passage, setup for next sequence
  - **Reflection**: Internal processing, emotional aftermath, quiet character moment

  Map the resulting rhythm across the narrative:
  ```
  Ch 1  [Tension]     ▓▓▓▓▓▓▓▓
  Ch 2  [Reflection]  ░░░░░░
  Ch 3  [Action]      ████████████
  Ch 4  [Revelation]  ▒▒▒▒▒▒▒▒▒
  Ch 5  [Transition]  ░░░░
  Ch 6  [Action]      ██████████████
  Ch 7  [Tension]     ▓▓▓▓▓▓▓▓▓▓
  ```

  Flag patterns:
  - **Monotone**: 3+ consecutive scenes at the same tempo
  - **Whiplash**: Jarring tempo shifts without transition
  - **Missing type**: If no reflection scenes exist in a character-driven story, or no action in a thriller
</tempo_classification>

---

### STEP 3: CLIMAX VS BREATHER BALANCE

<climax_breather_analysis>
  Cross-reference tempo map with OUTLINE.md structural intentions:
  - Are scenes marked as climaxes actually written at high intensity?
  - Is there a breather scene (reflection or transition) after each high-intensity sequence?
  - Are there too many consecutive scenes at the same intensity level?
  - Does the intensity generally build toward structural climax points?

  Flag:
  - **Missing breather**: High-intensity scene followed immediately by another high-intensity scene without relief (reader fatigue risk)
  - **Missing escalation**: Breather followed by breather followed by breather (momentum loss)
  - **Structural mismatch**: A scene marked as climax in the outline that reads at low intensity in the draft, or vice versa
</climax_breather_analysis>

---

### STEP 4: OPENING AND CLOSING ENERGY

<energy_analysis>
  For each chapter/scene:
  - **Opening hook**: Does the first paragraph create a question, conflict, or sensory pull that makes the reader want to continue? Rate: Strong / Adequate / Weak
  - **Closing propulsion**: Does the final paragraph create forward momentum -- a cliffhanger, question, emotional charge, or promise of what's next? Rate: Strong / Adequate / Weak

  Flag:
  - Chapters that open with exposition or backstory (energy drain)
  - Chapters that close without forward pull (reader puts the book down)
  - Consecutive weak openings or closings (pattern problem)
</energy_analysis>

---

### STEP 5: SAGGY MIDDLE DETECTION

<saggy_middle_check>
  Examine the 40-60% mark of the manuscript (by word count):
  - Does the pacing drop noticeably compared to the first and third acts?
  - Are there scenes in this section that lack clear stakes or forward momentum?
  - Does this section contain an unusual concentration of transition or reflection scenes?
  - Is the protagonist reactive rather than proactive in this stretch?

  If pacing drops in the middle:
  - Check whether it's **intentional** (the outline marks this as a breathing space, a slow burn, or a deliberate structural choice)
  - If unintentional, suggest specific interventions: raise stakes, add a midpoint reversal, cut or compress low-energy scenes, add a ticking clock
</saggy_middle_check>

---

### OUTPUT

Present findings in this order:

1. **Visual Tempo Map**: The combined scene length + tempo visualization showing the full narrative rhythm at a glance

2. **Pacing Health Summary**:
   - Overall pacing assessment (well-paced / front-loaded / back-loaded / saggy middle / monotone)
   - Strongest pacing section and why
   - Weakest pacing section and why

3. **Findings by Dimension**: Detailed findings for each analysis dimension, grouped by severity:
   - High: Structural pacing problems that affect reader engagement
   - Medium: Missed opportunities for better rhythm
   - Low: Fine-tuning suggestions

4. **Recommendations**: Prioritized list of specific changes, from most impactful to least

Save to `.manuscript/{scope}-PACING-REPORT.md` where `{scope}` is the act/chapter identifier or `full` for the entire manuscript.

## Response Contract

Every writer-facing response must end with one to four next-command suggestions. Each suggestion must include a short explanation of what that path will do.

Use this format:

```markdown
Next commands:
- `/scr:...`: One short sentence explaining what this path will do.
- `/scr:...`: One short sentence explaining what this alternate path will do.
```

If exactly one path is clearly best, provide one suggestion. If two, three, or four useful paths exist, show them as alternatives. Do not force a linear path when the writer has a real choice.

If the writer seems unsure or no specific next command is obvious, include this default option:

```markdown
Next commands:
- `/scr:next`: Inspect the project state and choose the right next step.
```

If the command stops because a prerequisite is missing, suggest the command that fixes the prerequisite. Keep every explanation practical and writer-facing.