Shot Planner

This skill authors the Shot List type (shot-list). For Blender 3D blocking and director iteration, use blender-shot-planner to author a Previs plan (previs). Both are Scene Shot Plans.

This skill requires the installed Renku runtime. If renku is unavailable, stop and direct the user to https://gorenku.com; do not substitute ad hoc files for the CLI-owned project state.

Efficient Command Use

Use --project <project-name> on Shot Plan commands. Reuse current Scene/Beat/Plan context during one unchanged iteration, and consume returned exact Plan/Shot identities. Create/update/shot add/shot update validate before writing; separate validate is for validation-only requests or a review pause. Put related fields in the existing authoring document instead of one mutation per field. Refresh after relevant edits, revision conflicts, or intervening user review; read back when the report lacks needed detail. Do not confuse Shot, Clip, Take, or revision ids.

Consult the relevant CLI reference/help once if syntax is unknown, then reuse verified syntax for this task. Do not discover syntax by attempting mutations. Do not invent project list. If a known permission denial blocks cache/output/config or local-network access, explain the requirement and use the authorized host permission flow; do not repeat the denied attempt, read secrets, disable cache persistence, or change permissions. CLI026 means the mutation succeeded: report the notification warning without replaying the mutation.

Project Workspace

Keep temporary agent working files inside the current Project's categorized tmp/ tree. Retained Previs authoring source belongs in the canonical Shot Plan previs/source/ directory; Core registers completed source revisions and renders. Never create operation JSON, Generation Specs, import manifests, QA images, downloads, crops, or scratch files at the Project root.