Help us improve
Share bugs, ideas, or general feedback.
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.
npx claudepluginhub imyousuf/storytelling-media-mcp --plugin storytelling-media-mcpHow this skill is triggered — by the user, by Claude, or both
Slash command
/storytelling-media-mcp:movie-production-pipelineThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
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.
production/ inside the movie project for generated artifacts.
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.Use these stages in order unless the user explicitly jumps to a later stage:
Ingest & Normalize
production/01_ingest/brief_summary.md, brief_structure.json, open_questions.md, early_risks.md, approval_packet.md.Research & Sensitivity
production/02_research/research_notes.md, sensitivity_notes.md, authenticity_checklist.md.Chapter Architecture
production/03_chapters/chapters.json, chapter_beats.md, approval_packet.md.Screenplay Development
production/04_screenplay/chapter_##.md, plus dialogue_notes.md.Continuity & Tone Harmonization
production/05_continuity/continuity_report.md, revision_plan.md, updated screenplay files if approved.Visual & Media Generation Plan
production/06_visuals/character_refs.md, shot_prompts.json, video_manifest.json, stitch_plan.md.Read references/stage-contracts.md before spawning sub-agents. It defines each sub-agent's responsibility, prompt shape, expected output, and write restrictions.
Spawn sub-agents only for bounded first-pass work. Typical pattern:
The main agent must synthesize all sub-agent output into one coherent approval packet.
End every stage response with:
Do not start the next stage in the same turn unless the user already approved that transition.
Use Markdown for human review and JSON for machine handoff. Use stable keys:
titleloglinecharacterschapterslocationsvisual_languagelanguage_protocolconstraintsopen_questionsapproval_statusFor exact Stage 1 schemas and templates, read references/stage-contracts.md.
When working inside a private movie project, do not push generated artifacts unless the user asks.