playtest-design

Installation
SKILL.md

Playtest Design

Purpose: Get useful signal from playtests. Most playtest sessions are wasted — observers confirm what they already believe, ask leading questions, and draw conclusions from noise. This skill provides structured methods to avoid those traps.

Sources: Observation-over-self-report and the developer-blindness counter-measures follow Celia Hodent, The Gamer's Brain (2017). Confirmation-bias protocol draws on standard experimental-design practice. Small-sample usability guidance derives from Nielsen & Landauer (1993), whose "five users find ~85% of usability problems" applies to usability testing specifically and does not transfer to balance or preference questions — a distinction this skill is careful about below.


Core Principle: Observe, Then Ask

Players are reliable reporters of their experience (what they felt) but unreliable reporters of causes (why they felt it). Design your process accordingly.

Most Reliable ←———————————————→ Least Reliable
  What they did    What they felt    Why they think
  (behavior)       (experience)      they felt it
                                     (attribution)
Installs
6
GitHub Stars
2
First Seen
Apr 7, 2026