Team Composition

Team Composition:

Orchestrating Cohesive Narrative Creation

Effective narrative development in game and interactive media production depends on the seamless collaboration of diverse creative roles. The "Team Composition" skill (team-narrative) on the Happycapy Skills platform enables users to coordinate a narrative team, ensuring that story, lore, and narrative-driven level design are consistently aligned. This article explains the function, rationale, usage, timing, and key considerations for this skill, with technical examples reflecting its application.

What Is the Team Composition Skill?

The team-narrative skill is a structured orchestration tool designed to coordinate the efforts of key narrative roles within a development pipeline:

• narrative-director: Oversees high-level story arcs, character design, dialogue strategies, and the overall narrative vision.
• writer: Produces dialogue, lore entries, item descriptions, and other in-game texts.
• world-builder: Establishes world rules, faction design, history, geography, and environmental storytelling elements.
• art-director: Ensures visual coherence for characters and environments based on narrative requirements.

This skill automates the workflow of these subagents, guiding them through a defined pipeline where each role contributes its expertise. At every phase, the user is presented with proposals and options, making the process interactive and quality-controlled. The system leverages tools such as Read, Glob, Grep, Write, Edit, Task, AskUserQuestion, and TodoWrite to manage content and user decisions.

Why Use the Team Composition Skill?

Narrative development is inherently collaborative and multi-disciplinary. Without structured coordination, inconsistencies can arise between story, gameplay, and visual elements. The Team Composition skill addresses these challenges by:

• Ensuring Consistency: Aligns story, lore, dialogue, and visuals so that narrative content is cohesive.
• Streamlining Collaboration: Clearly defines the responsibilities of each subagent, reducing role overlap and communication gaps.
• User-Guided Decision Making: At key phase transitions, presents choices to the user for approval, ensuring transparency and creative control.
• Automating Repetitive Tasks: Handles file operations and content management, freeing creative staff to focus on high-value work.

This skill is particularly valuable for teams working in distributed or asynchronous environments, or for solo developers seeking to simulate a full narrative team.

How to Use the Team Composition Skill

The skill is invoked via the following command syntax:

/team-narrative [narrative content description]

Example usage:

/team-narrative boss encounter cutscene

Workflow Breakdown

1. Invocation: The user provides a narrative content description (e.g., "faction intro dialogue").
2. Pipeline Execution: The system orchestrates each subagent in sequence:
   • The narrative-director outlines the vision and key narrative elements.
   • The writer drafts dialogue, lore, and text content.
   • The world-builder ensures contextual fit with world rules, history, and geography.
   • The art-director proposes visual alignments for characters and settings.
3. Decision Points: At each phase transition, the system uses AskUserQuestion to present the user's options. Full proposals and analysis are shared, and the user must approve (with concise labels) before proceeding.
4. File Operations: The skill leverages tools like Write and Edit to generate and refine content, and uses Read, Glob, and Grep to scan and select relevant files.

Sample decision point code:

def present_options(phase, proposals):
    print(f"Phase: {phase}")
    for idx, proposal in enumerate(proposals):
        print(f"Option {idx + 1}: {proposal['summary']}")
    choice = input("Select an option (1-N): ")
    return proposals[int(choice) - 1]['label']

Usage Guidance: If the command is issued without arguments, the skill responds with usage instructions and does not proceed. For example:

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

When to Use the Team Composition Skill

Apply this skill whenever there is a need to develop or revise narrative content that requires input from multiple creative disciplines. Typical scenarios include:

• Designing major story cutscenes or interactions
• Creating new game factions or regions
• Building tutorial or onboarding experiences
• Developing interconnected lore or world-building elements

It is especially useful at project milestones, during narrative sprints, or when integrating new content that must remain consistent with established canon.

Important Notes

• User Involvement: The user must actively participate at each decision point; automation never bypasses user approval.
• Role Clarity: Each subagent has a clear, non-overlapping function-for example, the art-director proposes visual concepts only after narrative and world-building phases are complete.
• No Argument, No Action: The skill will not spawn agents without a narrative content description. Always specify the content to be developed.
• Strict English Output: All outputs and content must be in English only.
• Professional Workflow: The skill is intended for professional or semi-professional narrative design pipelines.

By using the Team Composition skill, developers and writers ensure that complex narrative content is crafted with clarity, structure, and creative synergy.