BeatBandit MCP

Prompts

/

revision_strategy_pipeline

Prompt

Revision Strategy Pipeline

revision_strategy_pipeline

prompt
beta
auth: project:read
status: v1

Route a known revision request to the right screenplay-first or story-first BeatBandit change surface, route Scene List Revision merge survivors through reviewable scene authoring, and route remaining structural-sync queues through Sync Screenplay (`story_review_run` continuity_audit) before more prose edits.

When to use

Use when the caller already knows they want to change something, but has not yet chosen the right BeatBandit revision surface.

Use when the workflow may need to branch between screenplay edits, story changes, or larger rewrites.

Use when the caller provides exact Fountain/plain screenplay text and needs to decide between snapshot replacement and creative rewrite tooling.

Use when recent story or scene-structure changes may have created pending Sync Screenplay update tasks.

Use when Scene List Revision merged scenes and merge survivors may need prose authoring before continuity ripple checks.

When not to use

Do not use when the caller already knows the exact tool and phase.

Do not use when the caller wants BeatBandit to diagnose what is wrong first; use `review_to_revisions_pipeline` instead.

Do not use for idea-to-outline generation in a brand-new project.

Examples

“I need to tighten dialogue without breaking structure.”

“Should I edit beats first or screenplay first for this change?”

“I have exact Fountain text for this scene and need to replace the editor scene.”

“I applied scene-list changes and need to sync the screenplay next.”

“I merged several scenes and need the survivor scene rewritten before ripple checks.”

Anti-examples

  • Generate a brand-new shot list for this scene.

Related tools

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

screenplay_readscreenplay_edit_proposescreenplay_edit_applyscreenplay_snapshot_applyscreenplay_rewrite_runstory_revision_runstory_review_runscreenplay_generation_runstory_mutatestory_entity_query

Live-state resources

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


Arguments schema

revision_strategy_pipeline input
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "required": [
    "project_id",
    "user_intent"
  ],
  "properties": {
    "project_id": {
      "type": "string",
      "pattern": "^[0-9]+
quot; }, "user_intent": { "type": "string" }, "preferred_target": { "type": "string", "enum": [ "auto", "screenplay", "story", "review" ] } }, "additionalProperties": false }

← All promptsv1 · prompt