Files
Claude-Code-Game-Studios/.claude/skills/team-narrative/SKILL.md
Donchitos ad540fe75d Game Studio Agent Architecture — complete setup (Phases 1-7)
48 coordinated Claude Code subagents for indie game development:
- 3 leadership agents (creative-director, technical-director, producer)
- 10 department leads (game-designer, lead-programmer, art-director, etc.)
- 23 specialist agents (gameplay, engine, AI, networking, UI, tools, etc.)
- 12 engine-specific agents (Godot, Unity, Unreal with sub-specialists)

Infrastructure:
- 34 skills (slash commands) for workflows, reviews, and team orchestration
- 8 hooks for commit validation, asset checks, session management
- 11 path-scoped rules enforcing domain-specific standards
- 28 templates for design docs, reports, and collaborative protocols

Key features:
- User-driven collaboration protocol (Question → Options → Decision → Draft → Approval)
- Engine version awareness with knowledge-gap detection (Godot 4.6 pinned)
- Phase gate system for development milestone validation
- CLAUDE.md kept under 80 lines with extracted doc imports

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-13 21:04:24 +11:00

3.3 KiB

name, description, argument-hint, user-invocable, allowed-tools
name description argument-hint user-invocable allowed-tools
team-narrative 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. [narrative content description] true Read, Glob, Grep, Write, Edit, Task

When this skill is invoked, orchestrate the narrative team through a structured pipeline.

Team Composition

  • narrative-director — Story arcs, character design, dialogue strategy, narrative vision
  • writer — Dialogue writing, lore entries, item descriptions, in-game text
  • world-builder — World rules, faction design, history, geography, environmental storytelling
  • level-designer — Level layouts that serve the narrative, pacing, environmental storytelling beats

How to Delegate

Use the Task tool to spawn each team member as a subagent:

  • subagent_type: narrative-director — Story arcs, character design, narrative vision
  • subagent_type: writer — Dialogue writing, lore entries, in-game text
  • subagent_type: world-builder — World rules, faction design, history, geography
  • subagent_type: level-designer — Level layouts that serve the narrative, pacing

Always 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).

Pipeline

Phase 1: Narrative Direction

Delegate to narrative-director:

  • Define the narrative purpose of this content: what story beat does it serve?
  • Identify characters involved, their motivations, and how this fits the overall arc
  • Set the emotional tone and pacing targets
  • Specify any lore dependencies or new lore this introduces
  • Output: narrative brief with story requirements

Phase 2: World Foundation (parallel)

Delegate in parallel:

  • world-builder: Create or update lore entries for factions, locations, and history relevant to this content. Cross-reference against existing lore for contradictions. Set canon level for new entries.
  • writer: Draft character dialogue using voice profiles. Ensure all lines are under 120 characters, use named placeholders for variables, and are localization-ready.

Phase 3: Level Narrative Integration

Delegate to level-designer:

  • Review the narrative brief and lore foundation
  • Design environmental storytelling elements in the level
  • Place narrative triggers, dialogue zones, and discovery points
  • Ensure pacing serves both gameplay and story

Phase 4: Review and Consistency

Delegate to narrative-director:

  • Review all dialogue against character voice profiles
  • Verify lore consistency across new and existing entries
  • Confirm narrative pacing aligns with level design
  • Check that all mysteries have documented "true answers"

Phase 5: Polish

  • Writer reviews all text for localization readiness
  • Verify no line exceeds dialogue box constraints
  • Confirm all text uses string keys (localization pipeline ready)
  • World-builder finalizes canon levels for all new lore

Output

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.