MCP / Prompts / idea_to_screenplay_pipeline

Idea To Screenplay Pipeline

idea_to_screenplay_pipeline

promptbetaauth: project:readstatus: v1

Route a BeatBandit project from raw idea through outline stages into screenplay generation, branching by template mode and live readiness instead of only raw card counts.

When to use

Use when the caller wants the canonical concept-to-screenplay path and wants BeatBandit to choose the next stage.
Use for movie and episodic/TV projects where the workflow should branch by template.

When not to use

Do not use when the caller only wants one known wizard step.
Do not use for direct screenplay edits or revision passes on material that already exists.

Examples

“Take this movie project from idea to screenplay.”
“What is the next canonical writing step for this TV project?”

Anti-examples

Polish scene 7 dialogue.

Related tools

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

project_query template_list genre_contract_query genre_contract story_development_run screenplay_generation_run story_entity_query job_get

Live-state resources

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

template_manifest project_canon_summary screenplay_document

Arguments schema

idea_to_screenplay_pipeline input

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "required": [
    "project_id"
  ],
  "properties": {
    "project_id": {
      "type": "string",
      "pattern": "^[0-9]+quot;
    },
    "target_stage": {
      "type": "string",
      "enum": [
        "outline",
        "scene_list",
        "treatment",
        "screenplay"
      ]
    },
    "user_goal": {
      "type": "string"
    }
  },
  "additionalProperties": false
}