Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.
Usage:
/team-narrative [narrative content description]— describe the story content, scene, or narrative area to work on (e.g.,boss encounter cutscene,faction intro dialogue,tutorial narrative). Do not useAskUserQuestionhere; output the guidance directly.
When this skill is invoked with an argument, orchestrate the narrative team through a structured pipeline.
Decision Points: At each phase transition, use AskUserQuestion to present
the user with the subagent's proposals as selectable options. Write the agent's
full analysis in conversation, then capture the decision with concise labels.
The user must approve before moving to the next phase.
Use the Task tool to spawn each team member as a subagent:
subagent_type: narrative-director — Story arcs, character design, narrative visionsubagent_type: writer — Dialogue writing, lore entries, in-game textsubagent_type: world-builder — World rules, faction design, history, geographysubagent_type: art-director — Character visual profiles, environmental visual storytelling, cinematic tonesubagent_type: level-designer — Level layouts that serve the narrative, pacingsubagent_type: localization-lead — i18n validation, string key compliance, translation headroomAlways provide full context in each agent's prompt (narrative brief, lore dependencies, character profiles). Launch independent agents in parallel where the pipeline allows it (e.g., Phase 2 agents can run simultaneously).
Delegate to narrative-director:
Delegate in parallel — issue all three Task calls simultaneously before waiting for any result:
Delegate to level-designer:
Delegate to narrative-director:
Delegate in parallel:
If any spawned agent (via Task) returns BLOCKED, errors, or cannot complete:
Common blockers:
/architecture-decision first/create-storiesAll file writes (narrative docs, dialogue files, lore entries) are delegated to sub-agents spawned via Task. Each sub-agent enforces the "May I write to [path]?" protocol. This orchestrator does not write files directly.
A summary report covering: narrative brief status, lore entries created/updated, dialogue lines written, level narrative integration points, consistency review results, and any unresolved contradictions.
Verdict: COMPLETE — narrative content delivered.
If the pipeline stops because a dependency is unresolved (e.g., lore contradiction or missing prerequisite not resolved by the user):
Verdict: BLOCKED — [reason]
/design-review on the narrative documents for consistency validation./localize extract to extract new strings for translation after dialogue is finalized./dev-story to implement dialogue triggers and narrative events in-engine.