team-live-ops

Orchestrate cross-functional live-ops planning into a production-ready season document package.

Updated Dec 22, 2024
One-click install
npx skills add https://github.com/imgamer/AILearn --skill team-live-ops-imgamer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-live-ops
Source: https://github.com/imgamer/AILearn/tree/main/game-studios/Claude-Code-Game-Studios-e375f/.claude/skills/team-live-ops
Command: npx skills add https://github.com/imgamer/AILearn --skill team-live-ops-imgamer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning post-launch live-ops planning into a coordinated, production-ready plan across design, economy, analytics, community, narrative, and writing roles.

Core Features & Use Cases

  • Season/Event orchestration: Aligns multiple specialized subagents to produce a cohesive season plan for a named season or described live event.
  • Economy and analytics readiness: Produces reward/economy design plus success metrics and telemetry instrumentation requirements.
  • Player-facing execution package: Generates narrative framing, player communication calendars, and required written content for launch and in-season touchpoints.
  • Ethics guardrail workflow: Performs an ethics policy check for the economy design and blocks approval when unresolved violations are found.

Quick Start

Use the skill with the season name or event description, for example: invoke /team-live-ops "Spring Event Season — limited-time boss rush with new shop rotation" to generate a complete live-ops season plan for production.

Frequently Asked Questions about team-live-ops

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

FAQPage Schema
How do I coordinate live-ops season planning across multiple teams?

Live-ops season planning can be coordinated by orchestrating cross-functional subagents into a production-ready document package, aligning design, economy, analytics, community, narrative, and writing roles through interactive phase transitions.

What is included in a production-ready live-ops event document package?

A production-ready live-ops document package includes season scoping, narrative framing, economy and reward design, analytics instrumentation requirements, writing, and player communication calendars for in-season touchpoints.

How do I design game economy rewards and telemetry for a limited-time season?

Economy rewards and telemetry are designed by producing reward configurations alongside success metrics, applying an ethics policy check to the economy design, and outputting required analytics instrumentation for the season.

Does live-ops planning require approval before moving between production phases?

Yes, live-ops planning requires interactive phase transitions with AskUserQuestion approvals to proceed, and it performs an ethics guardrail workflow that blocks approval when unresolved economy violations are found.

Can I resolve review mode for live-ops planning without interactive prompts?

Review mode can be resolved non-interactively by passing arguments or using a production/review-mode.txt file, bypassing the standard AskUserQuestion approvals to generate the consolidated design output.

Where are finalized live-ops season plans and design outputs written?

Finalized live-ops season plans are written as a consolidated design output to the design/live-ops/seasons/ directory, requiring YAML frontmatter metadata for proper season or event structuring.