Skip to content
SlashClone
DiscoverUse in ClaudeSubmit a link
Sign in
Made by@gameforge

Playtest feedback

@gameforge/playtest-feedback

Turn messy playtest notes into a ranked list of what to fix next. Tags each note (bug, confusion, frustration, boredom, delight, idea), tallies them with a script, ranks issues by how many testers hit them and how badly, and lists the moments players loved so you protect them.

SkillOtherv1.0.0 (latest)Tested
Use in Claude Save Like Clone Comment
Activity
New: be the first to try it
  1. 1---
  2. 2name: playtest-feedback
  3. 3description: Turn raw playtest notes (pasted chat, form exports, session notes, recordings transcribed to text) into a ranked list of what to fix next. Tags each note, tallies them with a script, ranks issues by how many testers hit them and how badly, and lists what players loved. Use after a playtest, a game jam showcase, or a demo day, or when the user says "summarize the playtest", "what should I fix first?", or "my testers said...".
  4. 4license: MIT
  5. 5---
  6. 6
  7. 7# Playtest feedback
  8. 8
  9. 9Players are great at telling you where it hurts and bad at telling you why. This kit turns their notes into one table ranked by impact, so the next build fixes the thing four out of four testers hit, not the thing the loudest tester said.
  10. 10
  11. 11## Inputs
  12. 12
  13. 13Ask for anything missing:
  14. 14
  15. 151. **The raw notes**: pasted text, or files in `playtests/` (one file per tester is ideal).
  16. 162. **The build and levels** played, so notes can be pinned to a level.
  17. 173. **The goal of this playtest** (default: "is the first five minutes fun and clear?"). Rank against that goal.
  18. 18
  19. 19## Steps
  20. 20
  21. 211. **Normalize into `data/playtest.csv`** with this header:
  22. 22
  23. 23 ```
  24. 24 tester,level,type,severity,tag,note
  25. 25 ```
  26. 26
  27. 27 - One row per observation. Split a note that says two things.
  28. 28 - `type`: `bug` (it is broken), `confusion` (did not know what to do), `frustration` (knew, but it felt unfair), `boredom` (nothing to do or too slow), `delight` (smiled, laughed, said "again"), `idea` (a suggestion).
  29. 29 - `severity` for problems: `1` minor, `2` hurts the fun, `3` blocks progress or made them quit.
  30. 30 - `tag`: a short shared label such as `jump-too-floaty`. Reuse the same tag for the same root problem across testers. This step is the real work; take care with it.
  31. 31 - `note`: the tester's own words where possible. Use a nickname like `P1`, not a real name.
  32. 32 - Show the user the tag list (tag, count, one example) and ask whether any should be merged or split before going on.
  33. 33
  34. 342. **Tally:**
  35. 35
  36. 36 ```bash
  37. 37 node scripts/tally-playtest.mjs data/playtest.csv out/playtest-summary.md --json out/playtest-summary.json
  38. 38 ```
  39. 39
  40. 40 Issues are ranked by distinct testers times worst severity. Rows with an unknown type are listed under "Rows needing a look"; fix them and rerun.
  41. 41
  42. 423. **Read the summary and add a "Fix next" section** to the top of `out/playtest-summary.md`: at most three items, each with the likely cause and one concrete change to try. Prefer tuning (a number in config) over new features.
  43. 434. **Name what to protect**: the delight list. Any fix that touches those moments needs a careful look.
  44. 445. **Suggest the next test**: what to watch for, and how many testers (five is usually plenty to find the big problems).
  45. 45
  46. 46## Output
  47. 47
  48. 48```markdown
  49. 49## Fix next
  50. 50
  51. 511. **jump-too-floaty** (4/4 testers, blocks progress on 1-2). Likely cause: low gravity and long hang time. Try: raise gravity 25% and add a faster fall when the button is released.
  52. 522. **stuck-in-wall** (2/4, blocks progress on 1-3). Likely cause: collision resolves after the door opens. Try: resolve X then Y separately, and push out of solid tiles.
  53. 533. **cant-find-jump** (2/4, tutorial). Try: show "Space to jump" next to the first gap until the first jump.
  54. 54
  55. 55Protect: the landing squash and the coin sound.
  56. 56```
  57. 57
  58. 58Then the generated tables follow.
  59. 59
  60. 60## Guardrails
  61. 61
  62. 62- Keep testers anonymous in every output. Replace real names with `P1`, `P2`, and so on.
  63. 63- Never invent observations. If a note is ambiguous, tag it, and mark the row in your summary as "unclear" rather than guessing the cause.
  64. 64- One loud tester is one tester. The ranking counts distinct people on purpose; do not reorder by how strongly someone felt.
  65. 65- Write only to `data/` and `out/`. Raw notes in `playtests/` are read, never changed.
Sign in to comment on a line