team-live-ops

Orchestrate post-launch live-ops planning across cross-functional teams with telemetry-driven decision making.

39|6|Updated May 3, 2026
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill team-live-ops-cenconq25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-live-ops
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/team-live-ops
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill team-live-ops-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate post-launch live-ops planning across a cross-functional team to deliver structured seasons, events, or updates.

Core Features & Use Cases

  • Phase-driven planning: context loading, telemetry synthesis, content, monetization, community, and copy direction.
  • Cross-team coordination: aligns live-ops designer, monetization-designer, analytics-engineer, community-manager, and content-strategist.
  • Lifecycle output: final live-ops cycle document and an actionable story/epic plan.

Quick Start

Spawn the five subagents and begin Phase 1 with a context load to initiate a live-ops cycle plan.

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 cross-functional live-ops planning for a game update?

Cross-functional live-ops planning is coordinated by spawning subagents for design, analytics, monetization, community, and content strategy, applying telemetry-driven decision making to align outputs with KPI targets.

What is telemetry-driven decision making in live-ops season planning?

Telemetry-driven decision making in live-ops uses synthesized telemetry data to guide content, monetization, and community plans, ensuring the structured season or event cycle aligns with KPI targets.

Can I use this approach to plan live-ops events for a cross-functional team?

Yes, you can plan live-ops events by spawning five subagents and initiating a phased workflow that covers context loading, telemetry synthesis, risk review, and a final cycle document.

What's the best way to structure a post-launch live-ops cycle document?

The best way to structure a live-ops cycle document is through a phased workflow: context loading, telemetry synthesis, content and monetization plans, risk review, and a final actionable story or epic plan.

Do I need dedicated subagents to orchestrate live-ops cadence?

Yes, orchestrating live-ops cadence requires dedicated subagents for live-ops design, monetization, analytics, community management, and content strategy to coordinate tasks and ensure outputs align with KPI targets.