playtest-analysis

Playtest Analysis

Purpose

Turn raw playtest observation into actionable design, UX, tuning, and production decisions.

Use When

• you have fresh playtest footage or notes
• the team disagrees on what the playtest meant
• a feature needs evidence-based iteration

Inputs

• session notes
• video or observation logs
• telemetry if available
• test goals and participant profile

Process

1. separate observation from interpretation
2. cluster issues by comprehension, friction, balance, pacing, or content
3. identify severity and frequency
4. connect findings to specific systems or screens
5. recommend next actions with owners and confidence levels

Outputs

• playtest report
• prioritized findings
• design hypotheses to test next
• milestone-impact notes

Quality Bar

• produces a current source of truth, not disconnected notes
• names owners, risks, and next actions explicitly
• separates decisions from assumptions and open questions

Common Failure Modes

• outdated docs that no longer match reality
• plans with no owner or no exit criteria
• hiding risks until they become schedule blockers

Related Agents

• playtest-analyst
• ui-ux-designer
• systems-designer

Related Commands

• playtest-report
• verify
• onboarding

Notes

• Keep this skill aligned with the relevant rules layer and current project documentation.
• If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.