PlaybookPrompts

Map the emotional arc of a video script before writing it

Creative & Design videoscriptwritingstorytellingcreative-direction

Scripts that feel flat usually have a pacing problem, not a writing problem — every beat lands at the same emotional register. This prompt builds an arc map so you can write with intention rather than momentum alone.

Prompt
You are a video director and script editor. Before I write a single line of script, I need an emotional arc map for the video.

Video purpose (ad, explainer, brand film, social content, etc.): {{VIDEO_PURPOSE}}
Runtime in seconds or minutes: {{RUNTIME}}
Desired emotional state of the viewer at the end: {{DESIRED_END_EMOTION}}
Brief description of the content or story: {{CONTENT_DESCRIPTION}}

1. Divide the runtime into 4 equal segments. Label them Opening, Build, Pivot, and Close.
2. For each segment, name:
   a. The primary emotion the viewer should feel
   b. The information or story beat that produces it
   c. One specific craft technique that supports that emotion (pacing, silence, contrast, specificity of detail, etc.)
3. Identify where the emotional low point sits. If there isn't one, flag that — flat arcs are common and worth knowing in advance.
4. Write the 'contract' line: the single sentence from the Opening that implicitly promises the viewer what they'll get if they keep watching.
5. Write the final 10–15 seconds as a prose description (not script): what the viewer sees, hears, and feels.

Note: This works best for videos with a narrative or persuasive structure. Pure tutorial or how-to content has a different arc logic — for those, focus on steps 2 and 4 only.
Variables to fill in
  • {{VIDEO_PURPOSE}}
  • {{RUNTIME}}
  • {{DESIRED_END_EMOTION}}
  • {{CONTENT_DESCRIPTION}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{VIDEO_PURPOSE}}{{RUNTIME}}{{DESIRED_END_EMOTION}}{{CONTENT_DESCRIPTION}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.