Playtest Report

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — INTEGRATED SYSTEM FIRST: this skill is one piece of the complete "Claude Code Game Studios" template (49 agents, 74 skills, studio templates and a studio CLAUDE.md, per the repository README). Each skill assumes that template is installed, with its conventions, its project.yaml / project.local.yaml configuration, its .claude/docs/ mode documents, its hooks (for example hooks/yaml-helper.sh, outside this skill's folder) and its .claude/scripts/ helpers. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "Playtest Report" for me. It has two modes. "new" outputs a blank structured playtest report template (session info, first impressions, gameplay flow, bugs, feature feedback, quantitative data, overall assessment) and ends there — nothing is saved. "analyze [path]" reads your existing playtest notes at the path you give, cross-references the design documents, fills the template with structured findings (defects go in the Bugs table, not under pain points), and routes the findings: design changes toward /propagate-design-change, balance toward /balance-check, bugs toward /bug-report, polish items to the production polish backlog. In full review mode it spawns the template's creative-director agent (gate CD-PLAYTEST) before saving. In analyze mode it asks before writing the report to production/qa/playtests/playtest-[date]-[tester].md. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/playtest-report/ folder at the pinned commit: 1 file in total) Pinned version: install the code at commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a temporary folder, check out commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418, and copy the .claude/skills/playtest-report/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 503d55d2b3a0144dfdc287e6dc3ba8c6da998e2611fe62ef0cd0d546438286fe If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file: SKILL.md only. Nothing in the folder is a program; it is instructions the agent follows at use time. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no notes of mine are read or modified. - Integrated-system reality, from the file: at use time the skill resolves studio configuration by running the template's hooks/yaml-helper.sh (keys review_mode, automation), cross-references my project's design documents (design/gdd/game-concept.md, or the minimal-tier brief), follows the template's director-gate documents, spawns the template's creative-director agent in full review mode, and routes follow-ups to other template skills (/propagate-design-change, /balance-check, /bug-report) — files, an agent and skills that live outside this skill's folder and are absent in a standalone install, so parts of it cannot run outside the full template. - At use time, "new" mode writes nothing at all. "analyze" mode writes only after asking: the report at production/qa/playtests/playtest-[date]-[tester].md in my project. The notes it reads are a local file at a path I supply. No third-party service, account or credential is named in the file. - Do not create or analyze any playtest report, do not run any template hook or agent, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole playtest-report folder into the agent's skills directory, in a folder named exactly "playtest-report", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: playtest-report), the 1 file in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that it belongs to the full Claude Code Game Studios template and may not run standalone (it resolves its settings through the template's yaml-helper hook and its full review mode needs the template's creative-director agent), and that its new mode saves nothing while analyze mode writes only after asking). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.