---
name: chapter-and-pacing-organizer
description: Restructures long Supademo demos with chapters and tighter pacing so viewers can jump to what they care about. Use when a demo has grown past ~15 steps, has no chapters, or analytics show mid-demo drop-off.
---

# Chapter & Pacing Organizer

Long demos lose viewers. This skill breaks a demo into skimmable chapters and trims the fat.

## Prerequisites

- Supademo MCP connected
- The demo to restructure

## Workflow

1. **Read the demo end-to-end.** `get_demo` — map each step to the task it belongs to (e.g., steps 1–4 = "Connect your account", 5–9 = "Build your first report").
2. **Propose chapter breaks.** Chapters should follow task boundaries, not arbitrary step counts. 3–6 chapters is the sweet spot. Present:
   | Chapter | Steps | Title |
3. **Spot pacing problems.**
   - Consecutive steps showing near-identical screens → candidates to merge or cut
   - Setup steps a buyer doesn't care about → cut or collapse into one annotated step
   - The "aha" moment buried past step 10 → suggest moving it earlier with `reorder_steps` if the flow allows
4. **Apply on approval.** `update_chapters` for the chapter structure; `reorder_steps` for sequence changes; `delete_steps` only with explicit per-step confirmation.
5. **Verify.** Re-pull `get_demo` and confirm the chapter list and step order match the approved plan.

## Guardrails

- Never delete steps without listing exactly which ones and getting a yes.
- If the demo has voiceovers, warn that reordering may break narrative continuity — voiceover scripts may need regeneration (`generate_voiceovers`).
- Check `get_demo_hotspot_performance` first if available: don't cut steps that are actually engaging viewers.