Plan, run, and interpret game playtests. Use when validating prototypes, onboarding, difficulty, mechanics, UI clarity, retention, or fun; when writing playtest scripts, surveys, observation plans, or telemetry requirements.
Scanned 9/12/2026
Install to Claude Code
npx -y skills add thedixitjain/the-mega-skill-library --skill game-playtest-planning --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Game Playtest Planning?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/thedixitjain-game-playtest-planning)More formats (shields.io, HTML) on the badges page.
---
name: game-playtest-planning
description: "Plan, run, and interpret game playtests. Use when validating prototypes, onboarding, difficulty, mechanics, UI clarity, retention, or fun; when writing playtest scripts, surveys, observation plans, or telemetry requirements."
category: media-and-creative
source_repo: hashgraph-online/awesome-codex-plugins
source_path: "plugins/LVTD-LLC/skills/skills/game-playtest-planning/SKILL.md"
source_url: https://github.com/hashgraph-online/awesome-codex-plugins/blob/HEAD/plugins/LVTD-LLC/skills/skills/game-playtest-planning/SKILL.md
---
# Game Playtest Planning
Use this skill to turn uncertainty into a playtest that can guide build decisions. A useful playtest starts with decisions the team is willing to make based on evidence.
## Source Traceability
Primary source: *The Art of Game Design: A Book of Lenses, Third Edition* by Jesse Schell, especially chapter 28 on playtesting. The workflow is transformed and paraphrased.
Supporting sources include Games User Research playtest guidance and Nielsen Norman Group usability-testing methods.
## Workflow
1. Define what decision the playtest should inform.
2. Choose participants who match the design question.
3. Pick the method: observation, think-aloud, task test, blind first-session, survey, telemetry review, or comparative test.
4. Write a protocol that avoids leading the player.
5. Capture observation, telemetry, player interpretation, and post-test reflection separately.
6. Convert findings into prioritized design changes.
## Required Output
- `Research Questions`: what must be learned.
- `Participant Plan`: who to test and why.
- `Protocol`: setup, tasks, moderator script, data to collect, and debrief.
- `Telemetry`: events and metrics to instrument.
- `Analysis Plan`: severity rubric, decision rules, and next design actions.
## Local References
Before producing a playtest plan, read:
- `references/core/guide.md`
- `workflows/playtest-protocol.md`
---
**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/LVTD-LLC/skills/skills/game-playtest-planning/SKILL.md`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!