When invoked with new , generate this template:
Playtest Report
Session Info
- Date: [Date]
- Build: [Version/Commit]
- Duration: [Time played]
- Tester: [Name/ID]
- Platform: [PC/Console/Mobile]
- Input Method: [KB+M / Gamepad / Touch]
- Session Type: [First time / Returning / Targeted test]
Test Focus
[What specific features or flows were being tested]
First Impressions (First 5 minutes)
- Understood the goal? [Yes/No/Partially]
- Understood the controls? [Yes/No/Partially]
- Emotional response: [Engaged/Confused/Bored/Frustrated/Excited]
- Notes: [Observations]
Gameplay Flow
What worked well
- [Observation 1]
- [Observation 2]
Pain points
- [Issue 1 -- Severity: High/Medium/Low]
- [Issue 2 -- Severity: High/Medium/Low]
Confusion points
- [Where the player was confused and why]
Moments of delight
- [What surprised or pleased the player]
Bugs Encountered
| # | Description | Severity | Reproducible |
|---|
Feature-Specific Feedback
[Feature 1]
- Understood purpose? [Yes/No]
- Found engaging? [Yes/No]
- Suggestions: [Tester suggestions]
Quantitative Data (if available)
- Deaths: [Count and locations]
- Time per area: [Breakdown]
- Items used: [What and when]
- Features discovered vs missed: [List]
Overall Assessment
- Would play again? [Yes/No/Maybe]
- Difficulty: [Too Easy / Just Right / Too Hard]
- Pacing: [Too Slow / Good / Too Fast]
- Session length preference: [Shorter / Good / Longer]
Top 3 Priorities from this session
- [Most important finding]
- [Second priority]
- [Third priority]
When invoked with analyze , read the raw notes, cross-reference with existing design documents, and fill in the template above with structured findings. Flag any playtest observations that conflict with design intent.