playtest-report

The Skill structures raw playtest notes into actionable reports by preserving session metadata and categorizing findings into design changes, bugs, and polish items. It applies domain-specific templates to create decision-ready outputs.

Product validation reporting converts user-test, API, CLI, and workflow notes into structured findings. It identifies completion findings, friction points, adoption blockers, and operational concerns to help teams decide what to fix or investigate next.

To turn game testing feedback into prioritized items, the Skill organizes player observations into first impressions, flow, bugs, and balance issues. It then routes these categorized findings into specific action priorities for team follow-up.

Yes, you can use this for both game and product testing. It features domain-aware routing that detects whether your session is game-focused or product-focused, applying the correct report template and next-step guidance for API, CLI, or workflow validation.

Yes, it supports governed handoff through review-mode handling and approval-aware saving. This ensures your structured playtest reports route correctly to downstream follow-up processes while maintaining compliance.

The best way to categorize adoption blockers is using domain-aware action categorization. It separates user testing findings into implementation defects, reliability issues, and adoption blockers, routing them to appropriate next steps.