team-live-ops

Plan cross-functional live-ops content updates with a phase-gated approval process.

Updated Feb 8, 2024
One-click install
npx skills add https://github.com/kay6198835/Game-RPG --skill team-live-ops-kay6198835
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-live-ops
Source: https://github.com/kay6198835/Game-RPG/tree/main/.claude/skills/team-live-ops
Command: npx skills add https://github.com/kay6198835/Game-RPG --skill team-live-ops-kay6198835

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate a cross-disciplinary live-ops planning process for post-launch content by coordinating a team of specialists (live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director) to design and plan a season, event, or live content update.

Core Features & Use Cases

  • Cross-functional orchestration: aligns design, economy, analytics, storytelling, and communications to deliver cohesive live-ops plans.
  • Structured planning pipeline: follows a phased workflow (scoping, narrative theme, economy design, analytics, content writing, communications, and review) with explicit handoffs.
  • Parallel collaboration and governance: delegates work to subagents, reads season briefs, and enforces gated approvals to ensure quality and ethics compliance.

Quick Start

Provide a season concept and brief to initiate Phase 1 planning.

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 post-launch content updates?

Cross-functional live-ops planning is coordinated through a structured pipeline that aligns design, economy, analytics, narrative, and communications. The process delegates work to subagents and enforces phase-gated approvals to produce cohesive season briefs and content roadmaps.

What is the structured pipeline for seasonal planning and event design in live-ops?

Seasonal planning and event design follows a phased workflow covering scoping, narrative theme, economy design, analytics, content writing, communications, and review. Each phase features explicit handoffs and gated approvals to ensure quality and ethics compliance across all deliverables.

How do I manage deliverables and approvals across a multi-disciplinary live-ops team?

Deliverables across a multi-disciplinary live-ops team are managed by delegating specialized tasks to subagents like economy-designers and analytics-engineers. A phase-gated approval process governs the workflow, reading season briefs to enforce quality and ethics compliance before advancing.

Can I use this approach to align economy design and analytics for a live content update?

Yes, you can align economy design and analytics for live content updates by applying this cross-functional orchestration skill. It defines specific roles and deliverables, including an economy design plan and an analytics plan, ensuring both disciplines integrate cohesively during the planning pipeline.

What do I need to start planning a season brief for a live-ops content roadmap?

To start planning a season brief for a live-ops content roadmap, you need to provide a season concept and brief. This input initiates Phase 1 scoping, which then triggers the structured planning pipeline across narrative, economy, analytics, and communications teams.

Does live-ops planning work for both seasonal events and standalone content updates?

Yes, live-ops planning works for both seasonal events and standalone content updates. The orchestration process is designed to plan and coordinate cross-functional efforts for any post-launch content update, applying the same structured pipeline and gated approval workflow.