Game Demo Feedback Triage

Use this skill to turn a messy feedback packet into a short, weighted game-feedback brief.

The goal is not to summarize every note. The goal is to identify the highest-confidence player-facing blockers, separate representative signals from noisy anecdotes, and recommend the single next artifact that the team should produce before the next build, playtest, festival, or launch beat.

Read references/feedback-buckets.md before classifying edge cases or when store/demo, UX, stability, and performance signals are mixed together.

When to use this skill

• Internal playtest notes, survey responses, bug lists, and feedback docs need prioritization
• Steam Playtest, Next Fest, creator, or streamer demo reactions need to be converted into a ranked fix brief
• Teams have mixed qualitative and technical evidence and need to decide what matters before the next build
• Feedback touches onboarding, clarity, difficulty, controls, performance, stability, or conversion and the team needs one cross-functional view
• Small studios need a short go / no-go or fix-first recommendation instead of a giant product report