team-live-ops

Coordinate cross-functional planning for post-launch seasons and live content updates.

47|12|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill team-live-ops-nuoyanruoshui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-live-ops
Source: https://github.com/nuoyanruoshui/GodotGameFramework/tree/main/Godot/.claude/skills/team-live-ops
Command: npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill team-live-ops-nuoyanruoshui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates the complex cross-functional work required to plan a post-launch season, event, or live content update, reducing fragmented decisions and ensuring that design, economy, analytics, narrative, writing, and community communications stay aligned.

Core Features & Use Cases

  • Multi-Agent Planning: Orchestrates live-ops, economy, analytics, community, narrative, and writing specialists through a structured planning pipeline.
  • Approval-Gated Workflow: Presents proposals at phase transitions, supports full, lean, and solo review modes, and requires user approval before advancing.
  • Production-Ready Outputs: Produces season design, analytics, and communication documents while validating economy fairness, ethics-policy compliance, metrics, telemetry, and unresolved production questions.
  • Use Case: Use it to plan a seasonal event with a reward track, narrative arc, retention mechanics, success metrics, launch messaging, and documented handoff materials for production teams.

Quick Start

Invoke the team-live-ops skill with a season name or event description and optionally choose a full, lean, or solo review mode.

Frequently Asked Questions about team-live-ops

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

FAQPage Schema
How do I plan a game season update without fragmenting cross-functional decisions?

Coordinated season planning aligns design, economy, analytics, narrative, and community communications through a structured pipeline. It reduces fragmented decisions by orchestrating live-ops specialists and requiring approval gates before advancing phases.

What is the best way to design a live ops event with a reward track and retention mechanics?

Live ops event design involves orchestrating multi-agent planning for reward tracks, narrative arcs, and retention mechanics. The workflow validates economy fairness and ethics-policy compliance while producing season design and analytics documents.

How do I align analytics instrumentation and telemetry with game event design?

Aligning analytics instrumentation with event design requires validating metrics and telemetry during the planning pipeline. The workflow integrates analytics specialists to ensure success metrics are documented and tracked before production handoff.

Can I use a live ops planning workflow for solo game development?

Yes, live ops planning supports full, lean, and solo review modes. Solo developers can use the workflow to structure season content scope, player communications, and production handoff materials without a full cross-functional team.

How do I generate production-ready handoff documents for a game season launch?

Generating production-ready handoff documents requires completing the approval-gated planning pipeline. The workflow outputs season design documents, analytics plans, and launch messaging materials while documenting unresolved production questions for teams.

What should I include in player communications for a seasonal game content update?

Player communications for seasonal updates should include launch messaging and narrative framing coordinated with community specialists. The planning workflow integrates writing and community outputs to ensure messaging aligns with content scope and reward economies.