create-shot-list

Purpose

Author the scene manifest — the text-based shot list that drives downstream prompt assembly and per-scene rendering.

Replaces the role that visual storyboarding played in the older NB2 + i2v multi-keyframe architecture. With Seedance 2.0 reference-to-video, scene-by-scene image generation is no longer required — but a structured plan IS still required, because:

1. Multi-scene ads have global decisions that don't exist inside any single prompt (product ordering, setting variety, wardrobe rotation, lighting continuity).
2. Cost gating — at $5-10 per Seedance scene, a human needs to approve the plan before firing 4-6 scenes.
3. Global-rule enforcement — e.g. "wardrobe must vary across scenes" (per create-ugc-style-video Decision Rule 5). Each Seedance call has no memory of other calls; the author enforces variation in the manifest.

Use this atom when:

• The video has ≥2 distinct scenes (hook + product scenes, multi-product review, multi-setting GRWM, before/after, etc.)
• The architecture is Seedance 2.0 reference-to-video (one prompt per scene with internal sub-beats) — OR the legacy NB2 + i2v multi-keyframe flow (one keyframe per beat)
• A pre-render human gate is needed

Skip the manifest (or collapse to one row) for single-scene 15s ads with one product and no setting change.