Filmmakers keep getting this wrong. They open the AI tool, start describing scenes, iterate until something sticks. The whole workflow starts at the wrong end.
The problem isn’t the prompts. It’s what’s missing before the prompts. When you start with an empty text box and a vague idea, you’re asking the AI to do your creative thinking for you. It’ll generate something. It always does. But it won’t generate your something. It’ll generate the statistical average of everything it’s seen, shaped loosely by whatever words you happened to use. That’s why 20 iterations later, the scene still feels slightly off. Not bad. Just not quite right. The AI didn’t fail. You handed it an incomplete brief and hoped for a specific result.
AI Cinematic Filmmaking: Pre-Production argues that pre-production happens before you touch the AI. Not alongside it. Before it.
That’s not a minor tweak. It’s the entire methodology.
The loop everyone’s stuck in vs. the actual pipeline
Standard approach: describe a scene, generate, revise, re-prompt, settle for close enough. Repeat for every scene. Hope they feel like one coherent film when you’re done.
The problem compounds scene by scene. The first generation establishes a visual tone you didn’t consciously choose. The second drifts slightly from it. By scene seven, you’re chasing consistency across outputs that were never designed to connect. You’re not making a film at that point. You’re curating a collection of outputs and hoping they add up to something coherent. They usually don’t. Something always feels assembled rather than made.
The book’s approach: build the complete pre-production package first. Story architecture. Scene breakdowns. Visual language. Emotional throughlines. Then generate with purpose instead of guessing.
This is how traditional filmmaking has always worked. You don’t call the director of photography without a shot list. You don’t call the composer without a locked cut. The discipline exists because creative consistency requires a plan, not just good taste in the moment. AI filmmaking needs the same rigor. The tool changes. The process doesn’t.
The author uses Ambrose Bierce’s An Occurrence at Owl Creek Bridge as the working example throughout. Every prompt shown. Every output explained. Every creative decision made transparent. You see a real project getting built from scratch, not a framework described in theory. Bierce’s story is a smart choice for this: it has a clear three-act structure, heavy visual symbolism, a critical emotional reversal, and almost no dialogue. Those constraints isolate exactly the visual and structural problems AI generation needs to solve, without letting character performance carry the weight.
🎬 What the workflow covers
- Story structure and scene mapping before any generation starts. Not a rough outline. A complete scene-by-scene breakdown with emotional beats, visual requirements, and transitions identified before you write a single prompt.
- Prompt design built from creative decisions, not trial and error. Each prompt traces back to a specific story choice. If you can’t explain why the prompt says what it says, the underlying decision hasn’t been made yet.
- Pre-production documentation that keeps the project coherent across dozens of generations. A consistent visual bible, tone reference, and style guide that every subsequent generation can be measured against.
- Visual and emotional throughlines that survive the output process. The throughline isn’t something you hope survives generation by generation. It’s something you engineer before the first run.
How to apply this today
Before opening any AI tool, define four things: what this is for, what tone it carries, what structure it follows, what done looks like. Three minutes of planning cuts iteration time in half.
Here’s what that looks like in practice. Say you’re making a 90-second short about urban isolation. Before you open anything: write one sentence on what this needs to make someone feel. Pick three visual references from actual films or photographs, not AI outputs. Sketch the structure as three images: the opening, the shift, the close. Define the failure condition, meaning what would make this feel wrong when you see it. Now you have a target. The AI becomes precise because you are precise. You’re not searching for the right output. You’re refining execution of a clear intention. That’s a completely different kind of work, and it shows in the result.
The re-prompting trap disappears once you know what done looks like. Most people skip that definition because it feels like overhead. It’s actually the work. Everything after it is just execution!
The book is free today on Amazon. If you’ve ever re-prompted the same scene 20 times and still felt like something was off, this framework explains exactly why.
Grab it here while the price holds.
Preparation Before Generation(Free Book Deal Today)
by u/Winter-Routine7909 in PromptEngineering