A workflow checklist is most useful when another person can tell what exists, which checks passed and what still needs to happen. This worked handoff starts from the real coffee-sequence files produced by DreamForge’s Storyboard Builder. It ends with an inspectable planning packet, not a claim that a film is finished.
We reran the existing planning functions on November 6, 2026. The native JSON, TXT and Markdown exports reproduced the published files byte for byte. No provider, image analysis, video generation, voice recording or final edit was performed.
Start with an identifiable plan
The three-shot worked storyboard supplies the brief: prepare the cup, show the pour, and close on the resting cup. Its shot identifiers are coffee-01, coffee-02 and coffee-03. Their duration suggestions are four, five and four seconds: a 13-second draft plan before editing.
Keep that identification with every export. The native JSON contains the input mode, framing suggestion, shared subject/style, sequence brief and separate shot records. The TXT and Markdown files expose the same prompts alongside settings and review questions. They are three views of the planning record, rather than three independent approvals.
Put the real files in a register
The file register CSV records the four actual input/export files, their byte sizes, full fingerprints, public URLs and locations in the downloadable package. It does not list hypothetical video or audio files as completed assets.
| File | What another creator can inspect |
|---|---|
coffee-storyboard-input.json |
Exact shared and per-shot fields used for the run. |
coffee-storyboard-output.json |
Native version-2 output with three distinct shots and separated planning metadata. |
coffee-storyboard.txt |
Readable prompts, settings notes and checklists. |
coffee-storyboard.md |
Native production sheet, including purpose, reference and edit-note fields. |
Use the existing Storyboard Builder to enter the fields manually if you want another run. The site does not import these JSON files. When a future edit changes the brief or a shot, keep the previous packet and give the new export a distinct project revision rather than silently replacing a file someone is reviewing.
Record the status of the work, not a green project label
The project register uses these explicit states:
- Verified text export: the native files exist, their identities are recorded, and rerunning the planning functions reproduced them.
- Written plan only: the companion narration drafts and timing budget have been written and calculated. No voice has been recorded or heard.
- Not run: provider selection, rendering, reference-rights checks for future assets, listening review, timeline assembly, final-file review and publication.
This distinction prevents a successful download from becoming “video approved.” It also makes a useful handoff possible before rendering: another creator can review the shot plan and decide which references and provider settings are needed next.
The filled handoff checklist reuses our existing blank workflow checklist. The original reusable questions and license are retained. The filled section explains why the rendering and publication items remain incomplete; it does not check them merely because planning is complete.
Choose the next owner and observation
For the overview, the next creator should confirm the intended cup/server arrangement and choose supported framing and duration controls in their provider. For the pouring detail, the next review should watch the complete pour and its ending. For the closing view, inspect whether the cup remains recognizable and whether the cut makes sense beside the previous shot.
Those are review instructions, not observations about clips we generated. Record the provider, model, selected controls, reference permissions and actual result when that work occurs. Adobe’s generation guide illustrates why provider steps are separate: the interface selects a model and settings, and generated media is then available in its history. A planning paragraph does not perform those operations. Check the exact product and current controls you choose.
Assign the narration script separately. The voiceover timing exercise uses the same shot IDs so a writer can revise spoken copy without losing the connection to the visual plan. Word counts and planned pacing can expose an overfull script before recording; they cannot certify intelligibility or synchronization.
Deliver a packet with a clear stopping point
Download the complete planning handoff ZIP. It contains the four native planning files under planning-exports/ and seven new registers/worksheets. Open the README first, then inspect the file register and the incomplete stages. A text editor or spreadsheet is enough; there is no email gate, model access or paid checkout in this packet.
The decision supported by this run is narrow: the text-planning packet is reproducible and ready for another creator to inspect. The next media-production stage still needs its own authorization, inputs and results. Keep that boundary visible in the eventual delivery note, then replace each unfinished status only when the corresponding observation exists.