General writing
AuraScore 81/100

Interactive Narrative Branching Dialogue Script Architect

Develop a complex, multi-choice branching narrative game scene script with emotional state tags and character subtext.

Use this template when authoring interactive dialogue scenes for AAA or indie narrative video games. It provides clear branching path structures, dialogue state trackers, and character emotional subtext across multiple decision forks.

Template

Role: Principal Narrative Designer and Lead Game Writer with deep expertise in systemic branching interactive storytelling.

Context

  • Game world lore and environmental setting: {{game_lore_setting}}
  • Participating character roster and motivations: {{character_roster}}
  • Central moral dilemma and scene objective: {{core_moral_dilemma}}
  • Branching choice paths and trigger criteria: {{dialogue_branch_nodes}}
  • Worldbuilding terminology and voice constraints: {{tonal_voice_rules}}
  • Gameplay context and cinematic trigger conditions: {{scene_gameplay_trigger}}

Task

Generate a fully branching interactive dialogue script for a pivotal narrative encounter, detailing player choice nodes, character emotional reactivity, systemic flags, and cinematic camera directives.

Method

  1. Review {{game_lore_setting}} and {{scene_gameplay_trigger}} to set the immediate spatial staging and player agency state.
  2. Establish the primary tension in {{core_moral_dilemma}} ensuring no player option presents an obvious or morally cost-free solution.
  3. Profile each figure in {{character_roster}}, defining their active subtext, hidden stakes, and emotional thresholds.
  4. Construct the initial conversation anchor with distinct emotional delivery tags adhering to {{tonal_voice_rules}}.
  5. Design the primary decision fork using {{dialogue_branch_nodes}}, charting at least three distinct player dialogue intents.
  6. Draft deep sub-branches for each choice, incorporating conditional flags based on past player reputation or inventory.
  7. Script reactive non-player character responses that acknowledge player tone and alter character relationship values.
  8. Reconverge or diverge narrative flow into consequence-driven outcome states that affect future gameplay progression.

Constraints

  • MUST write all player options in active voice with clear intent indicators (e.g., [PARAGON], [RENEGADE], [DECEPTIVE]).
  • MUST track systemic consequence variables explicitly using bracketed state flags (e.g., [SET: Trust_Level +1]).
  • Dialogue lines MUST NOT exceed two sentences per spoken node to maintain game pacing.
  • Every branch MUST stay strictly aligned with the linguistic cadence dictated by {{tonal_voice_rules}}.

Output format

  • Scene Metadata: Setting, participating actors, preconditions, and active systemic variables.
  • Branch Node 1.0 (Root): Cinematic establishing beat and root dialogue delivery.
  • Branch Node 2.0 (Player Choice Fork): Minimum 3 distinct choices with explicit consequence flags.
  • Branch Paths 2.A, 2.B, 2.C (Consequence Trees): Full dialogue exchanges and emotional subtext for each path.
  • Scene Resolution & Variable State Summary: Final outcome summary and exported narrative flags.

Self-review

  • Do all branching options sound uniquely distinct in player voice and strategic intent?
  • Are all narrative flags systematically closed and clearly trackable by a game engine implementation team?
  • Does the dialogue incorporate lore terms from {{tonal_voice_rules}} seamlessly without info-dumping?
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

writing-content
writing-general
media-entertainment
game writing
interactive narrative
branching dialogue