team-narrative

Orchestrates narrative-director, writer, world-builder, and level-designer subagents through a five-phase story production pipeline.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/onemanking/the-operator --skill team-narrative-onemanking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-narrative
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/team-narrative
Command: npx skills add https://github.com/onemanking/the-operator --skill team-narrative-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating story arcs, dialogue, world lore, and level design across multiple contributors often produces inconsistent characters, contradictory lore, and narrative pacing that fights the gameplay. This Skill orchestrates a structured multi-agent pipeline so narrative content stays coherent from concept to final polish. ## Core Features & Use Cases - Phased Delegation Pipeline: Runs five phases (narrative direction, parallel world-building and writing, level integration, consistency review, polish) with user approval gates between each phase. - Specialized Subagent Team: Delegates to narrative-director, writer, world-builder, and level-designer subagents via the Task tool, running independent agents in parallel where possible. - Consistency Enforcement: Verifies dialogue against character voice profiles, cross-references lore for contradictions, enforces 120-character dialogue limits, and confirms localization-ready string keys. - Use Case: When designing a new quest for a game, invoke this Skill to get a narrative brief, lore entries, drafted dialogue, and level narrative integration points, each reviewed and approved phase by phase. ## Quick Start Ask the assistant to orchestrate the narrative team to create the story content, lore, and level narrative design for your new quest or chapter.

Frequently Asked Questions about team-narrative

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate multiple AI agents for game narrative design?

Delegate each discipline to a specialized subagent using the Task tool: narrative-director for story arcs, writer for dialogue, world-builder for lore, and level-designer for narrative level layout. Run independent phases in parallel and gate each phase transition with user approval.

How to keep game lore consistent across multiple writers?

Cross-reference new lore entries against existing canon during the world-building phase, assign canon levels to each entry, and run a dedicated review phase where the narrative-director verifies consistency across all new and existing entries.

What constraints apply to game dialogue writing in this pipeline?

All dialogue lines must stay under 120 characters, use named placeholders for variables, and reference string keys so text is localization-ready. The polish phase verifies every line against dialogue box constraints before finalizing.

Can I approve or reject each narrative phase before continuing?

Yes. Each phase transition uses AskUserQuestion to present the subagent's proposals as selectable options. The pipeline does not advance to the next phase until the user approves the current phase output.

When should I not use a multi-agent narrative pipeline?

Avoid it for small standalone text tasks like a single item description or one-off lore note, where the five-phase orchestration overhead exceeds the value. It suits interconnected content spanning story, lore, dialogue, and level design.