team-live-ops

Orchestrates live-ops planning workflows into coordinated studio deliverables with Task delegation and ethics policy checks.

Updated May 13, 2026
One-click install
npx skills add https://github.com/FrancisVarga/the-dream-machine --skill team-live-ops-francisvarga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-live-ops
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/team-live-ops
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill team-live-ops-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes post-launch live-ops planning chaos by coordinating the right studio roles to produce a coherent season plan with scoped content, fair economy design, measurable success metrics, and player-ready messaging.

Core Features & Use Cases

  • Season and event scoping: Turns a season name or live event description into a structured brief with content scope, cadence, and retention hooks.
  • Narrative + theme alignment: Produces narrative framing that connects the plan to the game world and defines story hooks.
  • Economy, analytics, and comms in one pipeline: Designs rewards and pricing, defines telemetry/A-B tests and success metrics, and drafts player communication and announcements.
  • Ethics-gated economy review: Flags missing or violating ethics policy during Phase 7 and blocks or requests revisions when needed.

Quick Start

Run the skill with the season name to generate a full production-ready live-ops plan, including season design docs, analytics specs, and communication calendars.

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 for a live service game?

Live-ops season planning involves coordinating content scope, reward tracks, telemetry, and player comms into a single deliverable set. This workflow delegates studio role tasks through an approval pipeline to generate a production-ready season design document.

How do I coordinate multiple studio roles for content cadence and event scoping?

Studio role coordination for content cadence uses a Task pipeline with approval gates to assign subagent roles for economy design, analytics, and comms, ensuring structured deliverables rather than ad hoc planning chaos.

What's the best way to design a live event economy with ethics policy checks?

Economy design with ethics policy checks flags reward and pricing violations against a designated policy file, blocking or requesting revisions during the review phase to ensure fair live-ops monetization.

Can I generate analytics instrumentation specs and A-B test plans for a live-ops event?

Analytics instrumentation specs and A-B test plans are generated as part of the coordinated pipeline, defining telemetry requirements and success metrics alongside season design docs and communication calendars.

What limitations exist when automating season planning and narrative framing?

Season planning limitations include dependency on an initial season or event description to start, and mandatory compliance with an ethics policy file that can block deliverables if design requirements are violated.

Do I need a post-launch content plan to use this live-ops workflow?

A post-launch content scenario is required, as this workflow applies specifically to seasonal updates, limited-time events, and retention-driven content cadence rather than pre-launch game development.