marketing-beat-brief

name	marketing-beat-brief
description	Create a concise beat plan for announce/demo/update moments, with core message, assets, proof points, and community follow-up. Use for festivals, demos, betas, or patch launches.

Marketing Beat Brief

When to use

Create a concise beat plan for announce/demo/update moments, with core message, assets, proof points, and community follow-up. Use for festivals, demos, betas, or patch launches.

Inputs to gather

• beat goal
• audience
• timing
• assets/proof points

Recommended roles

• community_manager
• creative_director
• art_director

Primary docs / outputs

• studio/docs/templates/marketing-brief.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

• message house
• asset list
• posting/checkpoint plan
• feedback capture loop

Validation bar

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