team-live-ops

**Argument check:** If no season name or event description is provided, output: > "Usage: `/team-live-ops [season name or event description]` — Provide the name or description of the season or live event to plan." Then stop immediately without spawning any subagents or reading any files. When this skill is invoked with a valid argument, orchestrate the live-ops team through a structured planning pipeline. **Decision Points:** At each phase transition, use `AskUserQuestion` to present the user with the subagent's proposals as selectable options. Write the agent's full analysis in conversation, then capture the decision with concise labels. The user must approve before moving to the next phase. ## Team Composition - **live-ops-designer** — Season structure, event cadence, retention mechanics, battle pass - **economy-designer** — Live economy balance, store rotation, currency pricing, pity timers - **analytics-engineer** — Success metrics, A/B test design, event tracking, dashboard specs - **community-manager** — Player-facing announcements, event descriptions, seasonal messaging - **narrative-director** — Seasonal narrative theme, story arc, world event framing - **writer** — Event descriptions, reward item names, seasonal flavor text, announcement copy ## How to Delegate Use the Task tool to spawn each team member as a subagent: - `subagent_type: live-ops-designer` — Season/event structure and retention mechanics - `subagent_type: economy-designer` — Live economy balance ...