MCP / Prompts / screenplay_to_video_pipeline

Screenplay To Video Pipeline

screenplay_to_video_pipeline

promptbetaauth: project:readstatus: v1

Guide BeatBandit through the canonical screenplay-to-video pipeline for one scene or episode scope, keeping identity/art-direction references distinct from reviewed realized-continuity checkpoints.

When to use

  • Use when the caller wants the full storyboard-to-video workflow rather than one isolated media step.
  • Use the same prompt for both scene and episode scopes by switching scope_type and scope_code.
  • Use when the caller wants to create the recommended Scene Moodboard master reference before recurring images and per-shot reference images.
  • Use when the caller asks to storyboard a scene: first generate/query the shot list, then use `image_generate(workflow=generate_shot)` for individual storyboard frames.
  • Use when sequential generated shots should carry forward the immediately previous reviewed clip through its accepted chronological continuity grid.

When not to use

  • Do not use when the caller already knows the exact tool and only needs one isolated step.
  • Do not skip the Scene Moodboard step unless a selected Scene Moodboard already exists or the user explicitly asks to avoid it.
  • Do not blindly generate shot-specific reference images for every shot when a selected Scene Moodboard already gives enough character, environment, prop, and lighting continuity.
  • Do not jump straight to video without at least checking whether the scope has a shot list, usable recurring references, selected Scene Moodboard assets, or selected shot assets.
  • Do not treat `image_generate(workflow=generate_scene_moodboard)` as the way to create individual storyboard panels; it creates a scene-level visual reference board.
  • Do not treat a primary or merely generated video take as reviewed continuity; acceptance is explicit through `shot_mutate(entity_type=video_continuity)`.

Examples

  • “Storyboard this scene end-to-end.”
  • “Take this episode from shot list through reference frames and video.”
  • “Create the recommended scene moodboard, then generate recurring images using that moodboard as a reference, then decide which shots still need their own reference frames.”
  • “Use the existing scene moodboard as the master reference and only generate extra shot images where needed.”
  • “Generate clean storyboard panels for the first three shots.”

Anti-examples

  • Generate one still image for shot 12.
  • Use a scene moodboard prompt override to force a single storyboard panel.

Related tools

Prompts are orchestration guidance only. They route into these public tools instead of replacing them.

shot_list_generateshot_list_queryproject_assets_queryimage_generateasset_uploadvoice_profilemedia_generateshot_mutatevideo_generateexport_createjob_get

Live-state resources

Prompt resolution may inspect these resources or their backing backend reads before steering the client.

shot_list_scopeshot_element_libraryvisual_style_effectivemedia_catalog

Arguments schema

screenplay_to_video_pipeline input
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "required": [
    "project_id",
    "scope_type"
  ],
  "properties": {
    "project_id": {
      "type": "string",
      "pattern": "^[0-9]+
quot;
    },
    "scope_type": {
      "type": "string",
      "enum": [
        "project",
        "scene",
        "episode"
      ]
    },
    "scope_code": {
      "type": "string"
    },
    "target_output": {
      "type": "string"
    }
  },
  "allOf": [
    {
      "if": {
        "properties": {
          "scope_type": {
            "enum": [
              "scene",
              "episode"
            ]
          }
        },
        "required": [
          "scope_type"
        ]
      },
      "then": {
        "required": [
          "scope_code"
        ]
      }
    }
  ],
  "additionalProperties": false
}
← All promptsv1 · prompt