Plan Camera Shots

Design shots that express the approved story while remaining spatially and temporally executable.

Inputs

Read the shared request envelope and validate payload against schemas/input.schema.json.

Require project ID and beats. Accept story blueprint, production assets, camera constraints, an existing plan, and retry segment IDs as optional context.

Workflow

1. Normalize beat order, duration constraints, and available assets.
2. Establish a spatial baseline for each location.
3. Define continuity constraints for axis, eyeline, screen direction, lighting, wardrobe, and prop state.
4. Split each beat into the fewest shot segments needed to express its dramatic actions.
5. Specify framing, camera position, movement, blocking, performance, focus, sound, and duration.
6. Record start state, action path, and end state for each segment.
7. Bind asset IDs and upstream beat IDs.
8. Run preflight checks and preserve unaffected segments during targeted retries.

Output rules

Return:

• skill: plan-camera-shots
• data.spatial_baselines
• data.continuity_rules
• data.segments
• data.preflight

The sum of segment durations must follow the selected duration policy. Each segment needs one dominant action chain. Continuity overrides creative novelty when the two conflict.

Boundaries

• Do not change story events or dialogue.
• Do not generate images or video.
• Do not use camera terms that contradict blocking or duration.
• Do not reference assets that are absent without a diagnostic.

Read references/field-guide.md for IDs, duration policy, and preflight gates.