Team Composition

argument-hint: "[season name or event description]"

Team Composition:

Orchestrating a Live-Ops Team for Game Content Planning

What Is This?

The "Team Composition" skill (team-live-ops) on the Happycapy Skills platform is designed to orchestrate a multidisciplinary live-ops team for post-launch game content planning. When invoked with a specific season name or event description, this skill coordinates a set of specialized roles to collaboratively design, evaluate, and plan a live event, season, or content update. It provides a structured, iterative workflow, guiding the user and team through each phase of planning with clear decision points and concise documentation of proposals and approvals.

The skill brings together the following roles:

  • Live-Ops Designer: Oversees season structure, event cadence, retention mechanics, and battle pass features.
  • Economy Designer: Manages live economy balance, store rotation, currency pricing, and pity timers.
  • Analytics Engineer: Defines success metrics, A/B test designs, event tracking, and dashboard specifications.
  • Community Manager: Prepares player-facing announcements and communication plans.

This skill is tailored for game studios and live-ops teams that require a systematic approach to planning and executing live content updates, ensuring cross-functional alignment and effective user engagement.

Why Use It?

Effective live-ops planning requires seamless collaboration among various specialists, each bringing unique expertise. The "Team Composition" skill addresses several common challenges:

  • Cross-Disciplinary Coordination: By orchestrating multiple roles, the skill ensures that design, economy, analytics, and community needs are aligned and considered at every stage.
  • Structured Decision-Making: The skill prompts the user with clear proposals at each phase, ensuring that decisions are well-informed and approved before moving forward.
  • Transparency and Documentation: All proposals, analyses, and user decisions are recorded within the conversation, creating a traceable planning history.
  • Error Prevention: The skill enforces argument validation, providing usage instructions if a required season name or event description is missing, thus preventing incomplete planning sessions.
  • Efficiency: Automating the workflow reduces manual coordination overhead and accelerates the content planning process.

How to Use It

To use the "Team Composition" skill, follow these steps:

  1. Invocation: Trigger the skill with the /team-live-ops command, followed by the name or description of the season or event you wish to plan.

    /team-live-ops Winter Festival 2024

    If you omit the argument, the skill will respond with:

    Usage: `/team-live-ops [season name or event description]` - Provide the name or description of the season or live event to plan.

    No planning process will start without a valid argument.

  2. Planning Pipeline: Once invoked with valid input, the skill orchestrates the live-ops team through a multi-phase pipeline:

    • Each role (live-ops designer, economy designer, analytics engineer, community manager) contributes proposals relevant to their domain.
    • At the end of each phase, the skill presents you with the subagent's proposals as selectable options.
    • The agent writes a full analysis of the proposals in the conversation.
    • You are prompted via AskUserQuestion to select or approve the next step.
    • No phase proceeds without user approval.
  3. Iterative Review and Approval: Continue through each planning phase, making selections and approvals as prompted. The skill captures your decisions using concise labels for clear documentation.

  4. Completion: The process ends once all phases are approved, resulting in a collaboratively planned event or season, ready for execution.

Example Interaction (Pseudo-code):

User: /team-live-ops Spring Showdown 2025
Skill: [Presents proposals from each team role]
Skill: [Asks user to approve or select options]
User: [Makes selection]
Skill: [Moves to next phase with analysis]
...
[Repeat until all phases are approved]

When to Use It

Use the "Team Composition" skill in the following scenarios:

  • Planning a New Season: When designing the structure, economy, and engagement strategy for a new game season.
  • Launching Limited-Time Events: For comprehensive planning of holiday events, tournaments, or special challenges.
  • Coordinating Content Updates: When multiple teams must align on new features, store changes, or player communications.
  • Post-Launch Optimization: For ongoing refinement of live-ops based on player feedback, analytics, and business goals.

This skill is best suited for teams that value structured collaboration and need to ensure that all aspects of live-ops are addressed in a cohesive manner.

Important Notes

  • Argument Requirement: Always provide a season name or event description when invoking the skill. Failure to do so will terminate the process with a usage message.
  • User Approval Workflow: The skill never advances phases without explicit user selection and approval, ensuring full control and accountability.
  • Role Coverage: The skill covers four key roles crucial to live-ops planning. If your team structure differs, adjust your workflow accordingly.
  • Strict Sequence: The pipeline enforces decision points at each transition, preventing skipped steps or overlooked decisions.

By using the "Team Composition" skill, you streamline live-ops planning, improve cross-team communication, and ensure that each content update is strategically sound and execution-ready.