Verified against Veo 3.1 · 2026-08-01
Plan a multi-shot narrative sequence using Veo Flow scene extension
A prompt for planning a multi-shot narrative built on Flow's scene-extension feature, which seeds each new 8-second segment from the previous clip's final frame — structured to explicitly state what must carry over from the prior shot, since anything left unstated gets silently redrawn rather than continued.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Write a set of chained Veo 3.1 prompts for a multi-shot narrative sequence to be generated using Flow's scene-extension feature, where each new segment is seeded from the final frame of the previous one. This is fundamentally different from writing several independent prompts about the same scene — the extension feature carries visual continuity forward from the actual last frame, but only the continuity facts stated in the new prompt govern what happens to that carried-over state; anything left unstated is not guaranteed to persist and is often silently redrawn.
OVERALL SEQUENCE
a runner training alone at dawn who is joined partway through by a second runner, broken into 3 chained 8-second segments.
SHOT ONE (the seed)
a lone runner jogging along an empty riverside path at dawn, mist over the water, ending on the runner mid-stride, seen from behind, approaching a bridge underpass ahead — describe precisely what the final frame should show, since this exact final frame is what the extension feature hands to the next prompt as its starting point.
SHOT TWO (extension from shot one's final frame)
CARRIED OVER FROM THE PREVIOUS SHOT: same runner, same pace, same dawn mist and lighting direction, still approaching the same bridge underpass. State every fact from shot one's ending that must still be true — the character's position, what they are holding, the time of day, the lighting direction — since the extension model treats the new prompt's text as the authority on what happens next, and a continuity detail the new prompt does not mention is not automatically protected just because it was true in the previous frame.
NEW ACTION: a second runner falls into stride alongside them as they both emerge from under the bridge, ending on both runners now running side by side, facing forward toward the rising sun.
SHOT THREE (extension from shot two's final frame), if needed
CARRIED OVER: {{shot_three_continuity_facts}}.
NEW ACTION: {{shot_three_new_action}}.
CAMERA CONTINUITY
State explicitly in each extension prompt whether the camera holds its position and framing from the previous shot's end or makes a deliberate new move, since an unstated camera instruction on an extension is one of the more common places the sequence produces an unintended jump rather than a continuous or deliberately cut transition.
AUDIO CONTINUITY
If an ambient sound or music element was established in shot one, restate it in each subsequent extension prompt rather than assuming it continues — native audio does not automatically carry across chained generations the way the visual seed frame does.
WHAT TO AVOID
Do not assume a detail survives into the next segment just because it was visible in the previous one's final frame — restate anything load-bearing to the story. Do not chain more than three or four segments without reviewing the actual generated output between each one; continuity drift compounds across a chain, and a small unstated detail lost in segment two becomes a larger, harder-to-fix inconsistency by segment four.
OUTPUT
The full set of chained prompts in generation order, followed by one line per transition naming exactly which continuity facts were carried forward explicitly.Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Flow's scene-extension feature works by seeding a new generation from the actual pixels of the previous clip's final frame, which is a real mechanical fact about how the continuation works, not a creative-writing convention — but that seed only supplies the starting visual state, and what happens across the new eight seconds is governed entirely by the new prompt's own text, which is why an unstated continuity fact is not protected simply because it was visibly true a moment ago. This is the specific failure mode the "carried over from the previous shot" section is built to prevent: a chained sequence that only describes the new action in each segment, without restating what must still be true from before, routinely loses small details between segments — a prop disappears from a character's hand, lighting direction subtly shifts, a background element present in the seed frame is redrawn out of existence — because the extension model has no separate memory of "why" the previous frame looked the way it did, only the pixels themselves as a starting point to build the next eight seconds from. Treating audio the same way, and restating an ambient or musical element in every subsequent extension prompt rather than assuming it persists, matters because native audio generation is tied to each individual generation's own prompt text, and there is no audio equivalent of the visual seed-frame carryover — a sound established in shot one has genuinely nothing pulling it forward into shot two unless the new prompt asks for it again. Capping the chain at three or four segments before reviewing actual output, rather than planning a long sequence entirely up front and generating it end to end, respects how continuity errors compound: a small unstated detail lost in segment two is not just a local error, it becomes the new seed state that segment three builds from, so by segment four an unreviewed chain can have drifted from the original plan in ways that are far more expensive to fix retroactively than they would have been to catch after segment two.
Verified against
Veo 3.1 3.1 · 2026-08-01
Google Flow 1.5 · 2026-08-01
Changelog
- 2026-08-01 — Initial publish, verified against Veo 3.1 via Google Flow scene extension.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
