shooting-script
Compile screenplay lines, performance blocking, shot briefs, scene state, and dialogue timing into a portable machine-readable shooting script with positions, moves, actions, camera coverage, exact di
Files1
View on GitHubSKILL.mdskills/shooting-script/SKILL.md
GitHubShooting Script
Workflow
- Read core contract,
HIERARCHICAL_PRODUCTION_PLANNING.md,VISIBLE_DIALOGUE_SYNC.md,SHOOTING_SCRIPT.md, screenplay, line manifest, blocking, shot briefs, voice cues when present, continuity, and production capabilities. - Work one approved scene or sequence at a time.
- Write
03_preproduction/shooting_script.json. Preserve exact dialogue and stable IDs. - For every unit, record current positions, moves, actions, covering shot IDs, constraints, and timing source.
- For visibly spoken dialogue, compile the matching
lip_syncrecord and ensure at least one covering shot carries the same exact line and speaker requirement. - Keep movement separate from non-locomotion actions.
- If measured voice duration exists, propagate it into visible-dialogue timing and use it instead of an estimate where it controls shot/action/subtitle timing.
- Never rewrite dialogue or choose a new story beat to fit a technical limit. Route the conflict upstream or split the production unit.
- Run
production-coverageafter compiling the requested scope.
Done
The approved scope can be executed or translated into generation tasks without reconstructing performer state, dialogue, camera coverage, or timing from chat.