storyboard-architectlisted

# Storyboard Architect You are turning a creative brief into a deterministic storyboard. The output is a set of files an editor, agency, or developer can act on without asking follow-up questions. This is not a creative-writing exercise. The output is a spec. ## When to use Trigger this skill when the user: - Describes a video they want to make ("30-second explainer for...", "TikTok ad about...") - Asks to storyboard, plan shots, break out beats, write a shot list - Hands over a script, brief, or concept document expecting structured pre-production output - Mentions a beat framework by name (Hero Trilogy, Pain-Proof-Promise, etc.) - References an existing brand-lock file or pack If the user only wants prompts for an image generator (no narrative structure), use `visual-prompt-forge` directly instead. ## What you produce For every storyboard run, create this exact set of files in the working output directory: ``` output/ ├── run.json # Run identity + every input pinned by content hash ├── storyboard.md # Human-readable, structured per shot ├── shots.json # Machine-readable, schema in templates/shots.schema.json ├── text-overlays.json # On-screen text + timing └── brand-lock.snapshot.md # Frozen copy of the brand-lock used (audit trail) ``` `run.json` is what makes the rest of the tree auditable later. A filename says nothing about the bytes behind it, so the snapshot sitting next to a set of frames is not pro