What problem does it solve? Turning a written video script into a production-ready shot list is error-prone: shots get missed, durations drift from the script, and downstream prompt engineers lack the technical details (camera angle, motion, lighting) needed to generate each shot. This Skill standardizes that breakdown into machine-readable JSON plus a human-readable Markdown table. ## Core Features & Use Cases - Scene-to-shot mapping: Splits each script scene into one or more shots based on subject changes, camera angle changes, engine duration limits, and location changes. - Per-shot technical specification: Defines camera angle, camera motion, lighting, action, dialogue, sound effects, and transitions for every shot. - Dual validated output: Produces shotlist.json (schema-conformant, for machines) and shotlist.md (for humans) with enforced consistency, unique sequential shot IDs, and total duration matching the script within ±5%. - Use Case: After writing a 30-second promotional video script, run this Skill to get a shot-by-shot breakdown that a video prompt engineer can directly convert into AI video generation prompts. ## Quick Start Read my concept.md and script.md files and generate a complete shotlist.json and shotlist.md breaking the script into individual shots with camera, lighting, and timing details.