| name | movie-production-pipeline |
| description | Iterative multi-agent workflow for turning a director's brief, movie bible, or chapter outline into structured movie production artifacts. Use when the user wants Codex to run staged agent-like movie development: brief ingestion, research, chapter structuring, screenplay drafting, continuity harmonization, visual prompt planning, Veo/Nano Banana generation planning, or iterative review gates before moving between stages. |
Movie Production Pipeline
Run a gated, multi-agent movie development workflow. The user owns creative approval. Do not move from one stage to the next until the user gives explicit approval such as "approved", "continue", "move on", or an equivalent instruction.
Operating Rules
- Start by locating the movie project directory and primary brief. If unclear, ask for the path.
- Create or reuse
production/ inside the movie project for generated artifacts.
- If an output file already exists, read it first and either update it intentionally or create a timestamped draft under the same stage directory. Never overwrite prior approved artifacts silently.
- If the user asks for planning only or says not to edit files, return the stage plan and proposed artifact contents in the response without writing files.
- Treat each stage as a review gate:
- run the stage,
- write artifacts,
- summarize decisions and open questions,
- ask for user feedback,
- iterate until approved.
- Use sub-agents for the first analytical pass of each stage when the user has explicitly asked for this skill or multi-agent execution and sub-agent tools are available. In Codex sessions with
spawn_agent, use explorer for analysis-only passes and worker only for disjoint file-writing assignments. If sub-agent tools are unavailable, state that limitation and perform the first-pass roles locally.
- Do not duplicate sub-agent work locally. Integrate their outputs, resolve conflicts, and mark assumptions.
