community-ops

name	community-ops
description	Plan playtests, betas, patch-note communication, feedback intake, and community moderation loops. Use around demos, betas, and release updates.

Community Ops

When to use

Plan playtests, betas, patch-note communication, feedback intake, and community moderation loops. Use around demos, betas, and release updates.

Inputs to gather

• event/beat
• audience size
• feedback channels
• moderation/resourcing

Recommended roles

• community_manager
• qa_lead
• release_manager

Primary docs / outputs

• studio/docs/templates/community-ops.md
• studio/docs/templates/playtest-report.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

• community plan
• feedback rubric
• response guidelines
• follow-up owners

Validation bar

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