playtest-report

To generate a structured playtest report, run the skill in analyze mode on your raw notes file. It reads the notes, categorizes findings into design, balance, bug, and polish buckets, and saves a standardized report to your production paths after user confirmation.

Standardizing playtest feedback involves applying a consistent template that captures session metadata, first impressions, and gameplay flow. This process categorizes observations into actionable buckets, ensuring teams can prioritize fixes without manual reformatting or lost observations.

Categorizing playtest observations works by classifying raw findings into distinct buckets: design changes, balance adjustments, bug reports, and polish items. The skill cross-references design documents to flag conflicts and optionally triggers a creative director review.

Yes, you can trigger a creative director review from playtest notes. The skill spawns gate tasks for review and routes critical findings, proposing design changes and documenting priorities for the development backlog after generating the report.

Yes, design documents are used to cross-reference during playtest analysis to flag observations that conflict with design intent. This ensures the structured report accurately identifies necessary design changes and balance adjustments.