team-live-ops

Coordinating a live-ops season plan requires orchestrating narrative framing, economy design, analytics instrumentation, and player communications through a phased, approval-gated pipeline. This ensures strategy aligns before deeper design work continues.

Live economy design requires checking against an ethics policy file to ensure compliance. If the policy is missing, the workflow emits an explicit skip warning and applies BLOCKED gating when ethical violations are found.

Yes, the live-ops workflow supports parallelizable economy, theme, and analytics tasks. This allows analytics instrumentation and narrative framing to progress simultaneously before converging at user-approved decision points.

Planning player communications involves structuring outputs through community managers and writers. The workflow generates structured deliverables, producing season design docs alongside analytics and comms outputs under a designated directory.

No dependencies are required to start post-launch live-ops scoping. You run the workflow with your season name or event description, then select proposed plan options to proceed through each phase.

You should avoid fragmented live-ops planning when coordinating complex strategy, economy, and analytics. A unified, reviewable season plan prevents siloed design by integrating multiple specialized roles into a single orchestration workflow.