Resolve conflicts in the story brief before generating shots. A request for a quiet, realistic ceremony and a spectacular battle can describe two valid films, but not necessarily one coherent short film. Identify what the audience must understand, what cannot change and which preferences can yield. More adjectives will not resolve contradictory obligations.
Separate requirements from preferences
Use three columns in your own notes: essential event, protected fact and optional treatment. An essential event could be the couple helping each other. A protected fact could be a supplied venue or an agreed fictional character. A treatment could be rain, slow motion or an elaborate entrance. These are planning categories, not automatic controls in Imagild.
Ask what each request contributes. If a spectacular effect exists only because another video used it, it may not deserve the same priority as the couple's central relationship. Do not quietly drop a required event to fit a more impressive visual. Present the trade-off in ordinary language and obtain an explicit choice.
A fictional superpowered wedding brief
An invented couple wants a humorous film in which one partner stops falling objects and the other redirects wind. They also request a solemn vow, a crowded reception, three locations and a short runtime. The essential story is their cooperation; the solemn vow establishes why the cooperation matters. A third location and several unrelated guest incidents are expendable.
One workable outline is: a gust threatens the ceremony; the partners' first independent attempts interfere; they coordinate, protect the ceremony and resume the vow. It preserves the two powers and emotional purpose without promising every optional spectacle. The viewer can describe a cause, a complication and a resolution rather than a catalogue of effects.
Make the choice visible before approval
Write the conflict as a question with alternatives: keep the vow and one rescue, or replace the vow with several comic incidents? Include the consequence of each choice. Avoid asking simply whether the script feels cinematic, because that does not expose what has been removed.
Mark every essential requirement against a scene in the proposed story. If none supplies evidence, revise the story. If several scenes repeat the same evidence, use the space for a missing event. This audit is more useful than counting adjectives or checking how long the script looks on screen.
Carry the agreed priorities into production
In the film workspace, review the user-facing story before accepting references or videos. Keep a separate copy of your priorities if the current interface does not provide a requirements table. A director's expanded instructions should serve the accepted plot, not introduce a new premise. Reject a returned scene that contradicts a protected fact even when its style is attractive.
The generated result still needs inspection. A requirement is not a guarantee that the model will fulfil it, and a script approval is not approval of every later frame. Use an appropriate external editor for missing assembly capabilities rather than inventing controls.
Can I solve a contradiction by adding more detail?
Only if the detail explains how both requests can coexist. Otherwise a longer brief hides the same choice. Choose priorities before spending on additional attempts.
Should every stakeholder have an equal number of scenes?
No. Allocate scenes to the audience's understanding. Record whose request changed and why so the accepted story remains a shared decision.
Sources and related reading
Compare the concept-selection stage in Adobe’s product-shoot concept tutorial. Its Firefly and Photoshop controls are vendor-specific; the requirement-priority method in this guide is our editorial framework.