gds-playtest-plan

Creates structured playtesting plans with session guides, observation templates, and analysis frameworks.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill gds-playtest-plan-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-playtest-plan
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/gds-playtest-plan
Command: npx skills add https://github.com/watchthelight/shatterfish --skill gds-playtest-plan-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing effective playtesting sessions is hard: teams often run unstructured sessions that produce vague feedback instead of actionable insights. This Skill generates a complete, goal-oriented playtest plan covering session structure, observation guides, note-taking templates, and post-session analysis so user feedback translates into concrete design decisions. ## Core Features & Use Cases - Structured Session Planning: Builds pre-session, gameplay, and post-session phases with defined durations, intervention rules, and team roles for internal, external, or focused playtests. - Observation & Metrics Framework: Provides signal tables (confusion, frustration, engagement, boredom), quantitative metrics, and a standardized note-taking template. - Post-Session Analysis: Includes severity assessment, pattern identification, and a report template with prioritized recommendations. - Use Case: A game team preparing to validate a new tutorial can generate a full playtest plan with participant criteria, observation focus areas, and a report format ready for the QA team. ## Quick Start Ask the assistant to create a playtest plan for your current game build, specifying the playtest type and what you want to validate.

Frequently Asked Questions about gds-playtest-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a playtest plan for my game?

Define your test objectives, choose a playtest type (internal, external, or focused), then structure pre-session, gameplay, and post-session phases. This Skill generates the full plan document including observation guides, note-taking templates, and team role assignments.

What is the difference between internal, external, and focused playtests?

Internal playtests use team members for quick iteration and bug finding over 30-60 minutes. External playtests recruit target-audience testers for unbiased feedback over 1-2 hours. Focused playtests validate a specific feature with selected participants in 20-45 minute sessions.

What metrics should I collect during a playtesting session?

Collect quantitative metrics like time to complete the tutorial, deaths or failures per section, features discovered, session duration, and completion rate. Combine these with qualitative observations of confusion, frustration, engagement, and boredom signals.

When should a facilitator intervene during a playtest session?

Intervene only for critical bugs that block progress, genuine player distress, session time running out, or when the player explicitly asks for help. Letting players struggle within reason reveals authentic usability issues.

How many participants do I need for a playtest?

The default configuration uses five participants, which is generally sufficient to identify recurring patterns in behavior and feedback. Smaller focused sessions can work for validating a single specific feature or scenario.