QA Plan

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 "QA Plan" for me. The skill itself generates a structured QA plan for a sprint, a feature or a single story: it reads the in-scope story files and their referenced GDDs, classifies each story by test type (Logic, Integration, Visual/Feel, UI, Config/Data), and produces a plan stating what to automate, what to verify manually, the smoke-test scope, playtest requirements and a definition of done, written to production/qa/qa-plan-[sprint-slug]-[date].md. With zero stories in scope it stops with NOT ASSESSED rather than producing an empty plan. In Phase 5 it presents the plan and asks (AskUserQuestion) whether to write it, and optionally also back-fills a QA Test Cases section into each in-scope story file; it then silently appends a QA-PLAN marker comment to production/session-state/active.md. It resolves the studio configuration (automation, workflow, qa.level, system_overrides) by running the template's hooks/yaml-helper.sh, outside this skill's folder. Its frontmatter pins model: sonnet. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/qa-plan/ 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/qa-plan/ 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 fa3a333c9f0e298979e8e174165bcd58042d686b788327644487644c25c8efa5 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 project of mine is audited, read or modified. - Integrated-system reality, from the file: at use time the skill runs the template's hooks/yaml-helper.sh to resolve automation, workflow, qa.level and system_overrides, follows .claude/docs/automation-modes.md, workflow-modes.md and config-resolution.md, and reads my project's sprint plans and story files under production/, the GDDs under design/gdd/ and docs/architecture/control-manifest.md — all files that live outside this skill's folder and are absent in a standalone install, so it cannot run as designed on its own. - At use time its persistent output is the QA plan file in production/qa/, written only through the Phase 5 choice; the optional back-fill edits each in-scope story file's QA Test Cases section, and the skill also silently appends a QA-PLAN marker comment to production/session-state/active.md without a separate ask — that silent append is disclosed here. No third-party service, account or credential is named in the file. - Do not build a QA plan, do not run any template hook, 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 qa-plan folder into the agent's skills directory, in a folder named exactly "qa-plan", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: qa-plan), 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 reads the template's production/ and design/ files), and that at use time it writes its QA plan only through its Phase 5 options, with a silent session-state marker append disclosed in this prompt). 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.