Movie Director

Route Shot List coverage to shot-planner; route Blender Previs creation and camera/blocking/timing revisions to blender-shot-planner. Route AI generation from either plan type to media-producer, preserving the exact plan identity.

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

Resolve project identity once per task and pass it with exact selected resource ids to specialists. Do not repeat project current or director discovery just because a specialist is invoked. Director context uses the current authoring project: establish it once when needed. Studio selection remains a separate required read when the user refers to the open surface. Confirm completion from sufficient specialist mutation reports; read again for missing state or intervening edits.

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.