liveops-calendar

name	liveops-calendar
description	Plan a lightweight live-ops cadence with beats, offers/events, rewards, and operational risks. Use for service-like updates without overengineering.

LiveOps Calendar

When to use

Plan a lightweight live-ops cadence with beats, offers/events, rewards, and operational risks. Use for service-like updates without overengineering.

Inputs to gather

• cadence
• event types
• reward philosophy
• ops capacity

Recommended roles

• executive_producer
• economy_designer
• community_manager

Primary docs / outputs

• studio/docs/templates/liveops-calendar.md
• studio/docs/templates/community-ops.md

Workflow

1. Inspect the current repo/docs state first and cite concrete evidence.
2. Choose the smallest useful output that moves the project forward.
3. Make the highest-risk issue, blocker, or readiness gap unambiguous.
4. Update or create durable docs when the result should persist.
5. Recommend the next best role or skill if more work remains.

Category rules

• Prioritize severe player-facing, security, certification, and release risks over cosmetic issues.
• Make evidence, repro, and owner/action clarity explicit.
• Return a clear go/no-go or priority recommendation when the task is evaluative.

Deliverables

• liveops calendar
• event themes
• owner cadence
• risk notes

Validation bar

• severity or readiness clearly stated
• evidence or repro captured
• owner/next action explicit