team-live-ops

Live-ops season planning is coordinated by spawning parallel subagents for specialized roles like economy design, analytics, and narrative, guiding a structured pipeline from scoping to final sign-off. This ensures production-ready plans are produced reliably.

Planning limited-time events involves running a phased pipeline from initial scoping to sign-off, executing narrative framing, economy design, analytics planning, and content writing in parallel. Deliverables are saved directly to the designated live-ops directory.

Yes, you can generate a consolidated season brief and communication calendar by orchestrating specialized subagents across design, analytics, and community roles. The pipeline delegates writing tasks to produce these required deliverables.

Existing design documents are not strictly required but are read when available to inform the post-launch content update pipeline. The orchestration process scopes the season or event brief using whatever background documentation you provide.

When an ethics violation is detected during live-ops content planning, the pipeline blocks completion and surfaces a BLOCKED state. It runs an explicit review against ethics policy and offers concise recovery choices until violations are resolved.

Subagent orchestration handles parallel work by spawning specialized agents for economy design and analytics engineering simultaneously during specific pipeline phases. This coordinates cross-disciplinary tasks efficiently to produce consolidated design and analytics plans.