Film Pipeline

Problem

In film production workflows, character design, nine-grid storyboards, action blocking, and trailer prompts are often handled separately. When these steps are not coordinated, character appearance, color, lighting, and scene keywords can drift between artifacts. film-pipeline addresses this orchestration problem by deciding whether a request needs a single output or a multi-step pipeline, then carrying locked parameters into downstream skills.

How it works

The skill runs through four stages:

• Intent analysis: classify the input as a script, character description, action scene, visual style request, or a mixed brief.
• Routing: call character-sheet, storyboard-9grid, action-director, or trailer-director for a single output, or chain them for a pipeline.
• Context passing: propagate locked parameters such as character appearance, color palette, worldview, lighting tone, and aspect ratio.
• Integration: produce a summary, ordered module outputs, a consistency checklist, and next-step suggestions.

Boundaries

It is an orchestration layer for creative prompts and production planning, not a rendering engine. If the input lacks character details, scene setup, or action goals, it should prompt the user for clarification. Cross-step consistency depends on how well downstream skills consume the passed parameters.