Branching Narrative Architect
Design complex branching narratives with consistency checks and scope management
What You Can Do
You can design, validate, and optimize complex branching narratives by mapping narrative topology, analyzing player agency across choice points, tracking narrative promises (narrative debt), and maintaining consistency across diverging story branches. This skill helps you forecast development scope, identify narrative contradictions before they become costly, and ensure player choices feel meaningful rather than illusory.
Features
Visualize critical junctures, convergence points, and dead ends to understand story structure complexity
Distinguish meaningful player choices from illusions of choice and validate decision impact
Document story promises and payoffs across branches to prevent dangling plot threads
Cross-check characterization, lore, and plot continuity across branching paths
Estimate development complexity, branch count, and dialogue requirements to align with timeline and budget
Create reference architecture for writing teams and engineering implementation
Study competitor branching structures to understand industry approaches
Example Output
Narrative Map Output:
- Main branches identified: 7 significant choice points
- Convergence opportunities: 4 points where paths reconnect
- Narrative debt items: 12 promises requiring payoff (7 satisfied, 3 dangling, 2 optional)
- Agency analysis: 5 meaningful choices, 2 choices that don't impact outcome
- Scope estimate: 45,000 words required, 18-24 week writing timeline
Consistency Report:
- Character contradictions: 3 flagged (protagonist motivation shifts)
- Lore conflicts: 2 identified (timeline inconsistencies in Branch C)
- Missed convergence opportunities: 4 suggested
Optimization Recommendations:
- Consolidate 3 low-impact branches into single path
- Add 2 convergence points to reduce parallel development burden
What's Included
- SKILL.md instruction file with branching narrative methodology:
- Narrative topology mapping template with juncture identification checklist:
- Player agency validation framework with choice impact matrix:
- Narrative debt tracking spreadsheet for promise/payoff documentation:
- Consistency validation checklist covering character, lore, and plot continuity:
- Scope forecasting worksheet with word count and timeline estimators:
Who It's For
- Narrative designers architecting branching game stories and dialogue systems
- Game directors planning scope and complexity of story-driven titles
- Interactive fiction developers building choice-driven narrative experiences
- Studio leads validating narrative design before production investment
- Writing team leads organizing branching narrative documentation for writers
Best For
- Pre-production narrative planning for games with 3+ significant story branches
- Mid-project validation when branching narratives become complex or contradictory
- Refactoring bloated branching narratives to reduce scope creep
- Analyzing reference titles to understand branching narrative patterns
- Documenting narrative architecture for hand-off to writing and engineering teams
You might also like
You convert business process descriptions into structured data specifications that technical teams can implement without follow-up questions. The skill generates detailed data dictionaries specifying what data exists, how it flows, what quality standards it must meet, retention timelines, and compliance requirements. This bridges the communication gap between business stakeholders and data engineers, architects, and compliance officers.
by gadievron
You can submit multi-branch narrative scripts to identify logical contradictions, character motivation inconsistencies, and false player choices that undermine immersion. The validator maps decision trees, tracks character knowledge states across divergent paths, and flags coherence failures—catching structural issues before QA testing or implementation. You'll receive detailed analysis of which branches work narratively and specific recommendations for fixing problematic choices or plot holes.
by suryast
You can upload your complete lore documentation—quest texts, character bibles, environmental storytelling, dialogue scripts, timeline documents—and Claude will cross-reference them to flag contradictions, retcons, timeline inconsistencies, and canon gaps. The skill creates an auditable lore database that tracks which content is authoritative, identifies what's been retconned, and highlights missing connective narrative tissue across your IP.
by gadievron
You can systematically architect complex worlds where every system influences others, creating authentic cause-and-effect chains that drive narrative. This skill helps you map dependencies between geography and trade, politics and conflict, culture and faction dynamics, then identify logical inconsistencies before they break immersion. You'll produce consistency documents, lore frameworks, and faction relationship maps that support multi-author projects and branching storylines.
by gadievron
This skill transforms Claude into a lore auditor that catches contradictions across your entire narrative ecosystem—character ages, timeline placement, geography, personality consistency, and thematic integrity. You submit your lore documents, established canon, and new content together, and Claude flags logical inconsistencies, temporal conflicts, spatial incoherence, and potential player-facing plot holes before expensive production phases like voice acting or animation begin.
by gadievron
This skill runs a deterministic multi-stage pipeline to validate that each vulnerability finding from your scanner is real, reachable in production code, and genuinely exploitable. You eliminate wasted effort on false positives, unreachable code paths, and findings with impossible prerequisites—ensuring your exploit development team only works on findings that matter.
by gadievron
You can upload complex dialogue documents and have Claude analyze their branching structure for logical inconsistencies, tonal drift, pacing issues, and player agency problems. Claude validates that character voices remain consistent across multiple writers' contributions, maps decision architecture to ensure choices matter narratively, and identifies dead-end conversations or unresolved dialogue threads. The result is a structured audit with actionable recommendations for optimization before dialogue implementation into branching engines like Yarn, ink, or Dialogue Flow.
by gadievron
You can design multi-path narratives that feel coherent and meaningful by modeling how player choices create cascading consequences across story branches. This skill helps you track character state changes, dialogue dependencies, and narrative convergence points—ensuring that player agency feels genuine, not illusory. You'll identify and eliminate plot holes, false choices, and continuity errors before they reach players.
by gadievron