playtest-report

Convert raw playtest notes into structured reports with prioritized findings.

47|12|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill playtest-report-nuoyanruoshui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playtest-report
Source: https://github.com/nuoyanruoshui/GodotGameFramework/tree/main/Godot/.claude/skills/playtest-report
Command: npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill playtest-report-nuoyanruoshui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms unstructured playtest observations into consistent reports, helping teams identify player confusion, design problems, balance issues, bugs, and polish opportunities without losing important context.

Core Features & Use Cases

  • Report Templates: Generate a standardized playtest report covering session details, first impressions, gameplay flow, bugs, feature feedback, quantitative data, and overall assessment.
  • Note Analysis: Read existing playtest notes and organize them into structured findings while flagging conflicts with documented design intent.
  • Action Routing: Categorize findings as design changes, balance adjustments, bug reports, or polish items and recommend the appropriate follow-up workflow.
  • Creative Review: In full review mode, request a creative director assessment against the game's pillars, core fantasy, and testing hypothesis.
  • Use Case: Give the Skill raw notes from a playtest session to produce a prioritized report that distinguishes player-experience concerns from reproducible implementation bugs.

Quick Start

Use the playtest-report skill with analyze and the path to your raw playtest notes to generate a structured report with categorized next steps.

Frequently Asked Questions about playtest-report

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

FAQPage Schema
How do I convert raw playtest notes into structured game testing reports?

To generate structured playtest reports, you need to process raw playtest notes by categorizing observations into standardized sections covering first impressions, gameplay flow, bugs, and quantitative data. This organizes unstructured feedback into prioritized, actionable next steps.

What is the best way to categorize player feedback from game testing sessions?

The best way to categorize player feedback is to route observations into specific follow-up workflows like design changes, balance adjustments, bug reports, or polish items. This distinguishes subjective player-experience concerns from reproducible implementation bugs.

Can I flag conflicts between player feedback and game design intent during usability analysis?

Yes, you can flag conflicts between player feedback and game design intent by cross-referencing raw playtest notes with relevant design documents. This requires a full review mode to assess feedback against the game's core pillars and testing hypothesis.

Does playtest report generation work without access to design documents?

Yes, playtest report generation works with just raw playtest notes to produce a structured report with categorized next steps. However, providing relevant design documents is required to unlock the full review mode and creative director assessment capabilities.

How do I separate reproducible bugs from general player experience concerns in playtesting?

To separate reproducible bugs from general player experience concerns, you analyze raw playtest notes and categorize findings into distinct follow-up workflows. This action routing directs bugs to bug reports and experience issues to design or balance adjustments.