agentleFS
scotidevscotidev/GameDevStudio/.agents/skills/team-narrative/SKILL.md

team-narrative

Skill1 starsChanged 8 months agoMITView on GitHub

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.

11 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use asset-spec, create-control-manifest and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • lilangMaxSkill

    asset-spec

    Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.

    Also in 9 projects that use this

  • lilangMaxSkill

    create-control-manifest

    After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).

    Also in 9 projects that use this

  • +10 more from lilangMax

The file

We split this skill into the rules it gives an agent

9 rules. 7 are common, 2 are distinctive, and 0 are very specific to this project.

  • 7

    Common

    Most of the 9 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

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

    line 8
  2. Common:

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

    line 23
  3. Distinctive:

    Always provide full context in each agent's prompt (narrative brief, lore dependencies, character profiles).

    line 29
  4. Common:

    world-builder: Create or update lore entries for factions, locations, and history relevant to this content.

    line 43
  5. Common:

    Place narrative triggers, dialogue zones, and discovery points

    line 50
  6. Common:

    Ensure pacing serves both gameplay and story

    line 51
  7. Common:

    Verify lore consistency across new and existing entries

    line 56
  8. Common:

    Check that all mysteries have documented "true answers"

    line 58
  9. Distinctive:

    Verify no line exceeds dialogue box constraints

    line 62

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

When this skill is invoked, 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.

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.