team-live-ops

Orchestrate cross-functional live-ops planning with phased approval gates and document output.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/scomofo/dragon-forge --skill team-live-ops-scomofo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-live-ops
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/team-live-ops
Command: npx skills add https://github.com/scomofo/dragon-forge --skill team-live-ops-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of coordinating multiple disciplines to design and plan a post-launch live-ops season or event coherently, with clear scope, economy balance, metrics, writing, and player communications.

Core Features & Use Cases

  • Multi-role live-ops orchestration: Aligns live-ops design, economy balance, analytics instrumentation, community communications, narrative framing, and event/player-facing writing into one season plan.
  • Structured planning pipeline: Runs a phased workflow (scoping, narrative theme, economy design, analytics, writing, comms) with decision points for user approval at phase transitions.
  • Ethics-gated economy review: Validates the Phase 3 economy design against an ethics policy file when available, and blocks approval when violations are found.
  • Output document handoff: Produces season design artifacts under design/live-ops/ including season scope, analytics plan, and communication calendar.

Quick Start

Invoke /team-live-ops with a season name or event description to generate a complete, approval-gated live-ops planning package across all required roles.

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 live-ops season across multiple game development disciplines?

Plan a live-ops season by running a phased workflow that aligns proposals across design, economy, analytics, narrative, writing, and community communications. This orchestrates cross-functional teams into one coherent season plan with approval gates at each phase transition.

What is ethics-gated economy design in live-ops planning?

Ethics-gated economy design validates your Phase 3 economy balance against an ethics policy file, blocking approval when violations are detected. It ensures post-launch monetization and reward systems meet ethical standards before player-facing implementation.

How do I scope post-launch content for a limited-time game event?

Scope post-launch content by initiating a phased planning pipeline that starts with event scoping, then progresses through narrative theme, economy design, analytics, and player communications. User decision gates ensure approval before moving between phases.

Can I generate a player communication calendar and analytics plan for a game season?

Yes, you can generate a player communication calendar and analytics instrumentation plan as output document artifacts. These are produced under a designated design directory alongside the season scope and economy design documents.

What happens if an ethics policy file is missing during live-ops economy review?

When the ethics policy file is missing, the live-ops economy review handles the absence by blocking Phase 3 approval. The workflow requires explicit ethics validation before proceeding to analytics and writing phases.

Is phased delegation with user decision gates required for live-ops content planning?

Yes, phased delegation with user decision gates is required for live-ops content planning. The workflow enforces user approval at each phase transition, ensuring structured scoping, economy design, and communication alignment before finalizing artifacts.