video_storytelling_arcs v1.0.0

name: video_storytelling_arcs description: Structures story arcs for short-form video under 90 seconds: hook-first beat timing, setup-escalation-payoff, open loops, and planting and payoff across a series. Use when writing, reviewing, or fixing scripts for reels, shorts, TikToks, or serialized episode runs.

Video Storytelling Arcs

Purpose

Short video is an attention auction. This skill turns a topic into a script built from proven beats so viewers watch to the end and come back for the next one. It covers three levels: a single video under 90 seconds, a multi-beat arc inside one video, and a series arc that plants details in one episode and pays them off later.

Workflow

1. Pick the arc shape from the runtime

• 15-30s (single beat): HOOK -> SETUP -> TWIST -> PAYOFF. One idea, one payoff.
• 45-90s (escalation arc): HOOK -> SETUP -> TURN -> ESCALATION (2-4 beats) -> PAYOFF. This is the default for anything with stakes.
• Series (3+ episodes): every episode is a self-contained escalation arc PLUS one plant and one loop handoff (see step 4).

Timing budget, 60-90s video (from references/timing.md):

| Beat | Seconds | Job | |-------------|-----------|------------------------------------------| | Hook | 0-3 | Open a question the viewer must answer | | Setup | 3-10 | Who/where, one concrete sensory detail | | Turn | 10-15 | The moment everything changes | | Escalation | 15-70 | 2-4 beats, each raising stakes or a new question | | Payoff | 70-82 | Answer the hook in a way that reframes it | | CTA / loop | 82-90 | Explicit ask, or a line that loops to the first |

Words run 120-160 spoken at a natural pace for 45-60s of voiceover.

2. Write the hook first and never move on until it works

The hook is the first sentence, <= 8 words, spoken over a moving visual. Three forms that work:

• Contradiction: "Posting daily can slow your growth."
• Forbidden fact: "He committed the perfect murder."
• Consequence: "This is why your reels die at 500 views."

Never a greeting, never context first, never "in this video I will". Test: if the hook vanished, would the video survive? If yes, the hook is weak.

3. Build escalation, not explanation

The 3-8 second mark is the retention recalculation window. Viewers silently ask: is the promise escalating? If you answer with explanation, tension drops and they scroll. Pattern per line: 0-2s interruption, 3-5s reinforcement, 6-8s consequence. Every line should tighten the idea, not soften it.

Escalation checklist per beat:

• Does this beat raise the stakes OR open a new question? (If neither, cut it.)
• Is there a micro-hook every 5-8 seconds? ("Then...", "But the receipts...", "On the eighth night...")
• Is the most shocking line the shortest one? (Restraint at the peak. Long flowing line, then a two-word punch.)
• Are the facts specific? (Numbers, names, textures. "Forty years", "a film over it". Specificity reads as belief.)

4. Open loops deliberately, and track them

An open loop is a question raised early and answered late (or in a later episode). Psychology behind it: the Zeigarnik effect, people remember interrupted tasks far better than completed ones, so an unresolved question holds attention after the video ends.

Rules:

• One active loop at a time per video. A second loop needs an explicit handoff ("that is episode two's problem").
• Close small loops fast, bank the macro one. Answer a setup question within a beat or two, but the episode's core question waits for the payoff. Closing small loops builds trust; the macro loop builds retention.
• The loop ledger. Keep a running list of every loop opened and mark it answered when paid off. See references/loop_ledger.md. Never open a loop you have no plan to close: a loop closed with something disappointing erodes trust faster than curiosity ever built it.
• Loop the ending into the start when it fits. The best last line reframes the hook so rewatching feels new. That is a free replay.

5. Plant and payoff across a series

Planting is putting a detail in early that feels like texture and using it later. Payoff is the moment it fires. The satisfaction comes from reusing an established element, which beats introducing a new one every time.

Series mechanics:

• Plant in episode N, remind once, fire by N+3. A reminder between plant and payoff (a visual callback, a one-line mention) reinforces importance without explaining it.
• Plant as texture, never as announcement. If viewers can tell it is a plant, it becomes a prediction instead of a surprise. The bezoar in a potions class feels like trivia until it saves a life five books later.
• Every plant needs a payoff, and every payoff needs a plant. A surprise with no plant is a deus ex machina. A plant with no payoff is a broken promise.
• Track plants in the loop ledger. Column: plant, episode planted, episode paid off, status.

Worked examples of arc shapes, hook rewrites, and a series ledger are in references/examples.md.

Output Contract

When this skill produces a script, deliver:

1. Beat sheet: each beat labeled (HOOK / SETUP / TURN / ESCALATION 1..n / PAYOFF / CTA), with seconds and spoken line.
2. Word count and estimated runtime (assume ~2.7 words/second of voiceover).
3. Loop ledger entries: every loop opened, where it closes (timestamp or episode).
4. Plant list (series mode): plant, texture it hides behind, planned payoff episode.
5. One-line read: what the viewer feels at the payoff. If you cannot name it, the arc is not finished.

Operating Rules

1. Hook first, and never weaken it to make room. If the hook fails, nothing after it matters.
2. Explain nothing before second 8. Escalate instead.
3. One idea per video. A second idea is a second video.
4. Never invent facts to dramatize. If a claim is unverified, cut it or frame it as opinion.
5. Never open a loop without a planned payoff. Record it in the ledger the moment it is written.
6. The last line should reframe the first when possible, never just stop.
7. Keep the style plain and direct: no em dashes, no press-release sentences, no inspirational filler.