← Prompts

Storyboard to Video Shot Plan

Category creative
Subcategory video-previsualization
Difficulty intermediate
Target models: sora, veo, grok-imagine
Variables: {{story_goal}} {{audience}} {{tone}} {{duration_seconds}} {{key_beats}} {{production_constraints}}
video-generation storyboarding shot-planning previs creative-ops
Updated April 23, 2026

The Prompt

You are a previsualization director helping convert story beats into a practical AI video generation shot plan.

Inputs:
- Story goal: {{story_goal}}
- Audience: {{audience}}
- Tone/style: {{tone}}
- Target duration (seconds): {{duration_seconds}}
- Key beats: {{key_beats}}
- Production constraints: {{production_constraints}}

Output format:
1) Sequence overview (beginning/middle/end structure).
2) Shot list table with columns:
   - Shot ID
   - Duration
   - Visual action
   - Camera framing/movement
   - Primary generation lane
   - Reference inputs or continuity assets
   - Prompt draft for generation model
   - Audio note if relevant
   - Backup lane
   - Continuity notes
   - Risk flag
3) Transition notes between shots.
4) Edit handoff checklist for human editor.
5) Regeneration strategy if one shot fails quality.

Rules:
- Keep continuity explicit (subject, lighting, color palette, location).
- Favor clear camera directions and concrete scene actions.
- Keep total shot durations aligned to {{duration_seconds}}.
- Include one alternate shot option for the highest-risk beat.
- Flag any shot that depends on reference-image, first-frame, or extension controls.

When to Use

Use this for short-form video projects where you need quick previs structure before investing in full editing. It is especially useful for campaign teasers, product explainers, and social clips that require narrative coherence across several generated shots.

It is more useful now that storyboard-first, reference-heavy, and consistency-heavy video lanes behave differently. A structured plan helps the operator decide when to use Sora 2 storyboard/remix, Flow with Veo 3.1, Runway consistency tools, or a simpler fallback lane.

Variables

  • story_goal: Core message and intended viewer reaction.
  • audience: Who should understand or feel something from the video.
  • tone: Visual and emotional direction (documentary, cinematic, playful, minimal).
  • duration_seconds: Target runtime for final output.
  • key_beats: Ordered events/scenes that must appear.
  • production_constraints: Platform limits, legal constraints, brand rules, required assets.

Tips & Variations

  • Add a platform-specific version (9:16, 1:1, 16:9) by duplicating shot prompts with framing adjustments.
  • If the sequence depends on recurring characters or product visuals, add a locked reference pack and ask the model to reuse it across the whole shot list.
  • If motion quality is unstable, shorten high-complexity shots and increase cut count.
  • Add a “human-only pickup shots” list for moments AI generation cannot reliably produce.
  • Use a locked color script in prompts when multiple models are used in one sequence.
  • Keep audio assumptions separate from the visual prompt if the chosen lane does not handle synchronized sound well.

Example Output

A strong result includes a 6-8 shot table with generation prompts, lane guidance, transition notes, and an edit handoff checklist covering continuity, pacing, and compliance review. This lets a creative lead approve structure before full render cycles.