gds-playtest-plan

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

Updated May 7, 2026
One-click install
npx skills add https://github.com/jgabriellima/deep-agent-skill --skill gds-playtest-plan-jgabriellima
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gds-playtest-plan
Source: https://github.com/jgabriellima/deep-agent-skill/tree/main/skills/gds-playtest-plan
Command: npx skills add https://github.com/jgabriellima/deep-agent-skill --skill gds-playtest-plan-jgabriellima

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing effective playtesting sessions is hard: teams often run unstructured playtests that yield vague feedback instead of actionable insights about game feel, difficulty, and player experience. This Skill guides you through building a complete, goal-oriented playtest plan. ## Core Features & Use Cases - Structured Session Design: Defines pre-session, gameplay, and post-session phases with scripts, consent steps, and intervention rules. - Observation & Note-Taking Templates: Provides signal tables (confusion, frustration, engagement) and quantitative metrics like completion rates and time-on-task. - Post-Playtest Analysis Framework: Includes severity assessment, pattern identification, and a report template with prioritized recommendations. - Use Case: A game team with a new playable build asks for a playtest plan; the Skill produces a playtest-plan.md covering participant criteria, session structure, observation guides, and a post-session report format. ## Quick Start Ask the agent to create a playtest plan for your current game build, specifying whether it is an internal, external, or focused playtest.

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 the session into pre-session, gameplay, and post-session phases. The Skill generates a playtest-plan.md with observation guides, note-taking templates, and team roles.

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

Internal playtests use team members for quick 30-60 minute iterations, external playtests recruit target-audience testers for unbiased 1-2 hour sessions, and focused playtests target specific features with selected participants in 20-45 minute sessions.

What metrics should I collect during a playtest 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?▼

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.

What inputs does the playtest planning workflow need?▼

The workflow auto-locates your GDD and game brief from the output folder to identify mechanics to validate, and requires a playable build, defined test objectives, and participant criteria before proceeding.