Review All GDDs

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 "Review All GDDs" for me. The skill itself reviews all of a game's system GDDs together — something a per-GDD review cannot do: cross-GDD consistency (dependency symmetry, rule contradictions, stale references, tuning-knob ownership, formula compatibility, acceptance-criteria conflicts) and game-design holism (competing progression loops, player attention budget, dominant strategies, economic loops, difficulty curves, pillar drift, player-fantasy coherence), plus a cross-system scenario walkthrough. Its SKILL.md runs the load phase, then spawns two parallel game-designer sub-agents (the template's Agent mechanism and agent definitions, outside this skill's folder) for the consistency and design-theory passes, pasting them the loaded GDD sections, and follows the seven phase files under references/ in turn. In since-last-review mode it runs the template script .claude/scripts/review-scope.sh, also outside this folder. It asks (AskUserQuestion) before writing the combined report to design/gdd/gdd-cross-review-[ISO date].md, asks again before marking flagged GDDs "Needs Revision" in the systems index, and then silently appends a session extract to production/session-state/active.md. It resolves the studio configuration (automation, workflow, system_overrides) by running the template's hooks/yaml-helper.sh. Its frontmatter pins model: opus. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/review-all-gdds/ folder at the pinned commit: 8 files 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/review-all-gdds/ 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 2b5bae8837d3b47bee678ab78aa23f0e177326b4655f22d5c16470089a25241b - references/1-load.md: SHA-256 1bafd370ec7fa114b23e1d109eff3c1f9dfadca2c432427f214521d197a27ddd - references/2-consistency.md: SHA-256 38596caeb557efbca1ecb7b767f558865453b2266a35a59f7e34f173b44a2351 - references/3-design-holism.md: SHA-256 8855ba326fc36a2406c15afbcbdb22f01875ed079e4cd1446d8ffed668e819ee - references/4-scenarios.md: SHA-256 6cbabdb03c253ab2c2fe384ae075d68fbeeef705fc5acd60fcb60f9784ae286d - references/5-report.md: SHA-256 ae51d4b943c57dbedb5f08a78ec7b4608324c0a9bb97b509c40bb1772e4040cb - references/6-write.md: SHA-256 e4f3a48fd218f010138b5ef0453178dc7d4617db93044a1c57b7f2d35cbd2942 - references/7-handoff.md: SHA-256 76a11e26daef756825db1aabf6380c3781a1ac479eea38a63104ad697163b4c6 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 8 files: SKILL.md plus 7 phase files under references/ (1-load, 2-consistency, 3-design-holism, 4-scenarios, 5-report, 6-write, 7-handoff). Nothing in the folder is a program; the phase files are instructions the skill reads and 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 files: at use time the skill runs the template's hooks/yaml-helper.sh, follows .claude/docs/automation-modes.md, workflow-modes.md and error-recovery-protocol.md, spawns two parallel game-designer sub-agents from the template's agent definitions, can run the template script .claude/scripts/review-scope.sh, and reads my project's GDDs and entity registry under design/ — agents, scripts and docs that live outside this skill's folder and are absent in a standalone install, so it cannot run as designed on its own. The GDD content it passes to its sub-agents stays inside my own agent session; nothing is sent to a third party. - At use time it writes only after asking: the review report at design/gdd/gdd-cross-review-[ISO date].md on a first AskUserQuestion approval, and the systems-index "Needs Revision" status updates only on a second approval; it then silently appends a session extract 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 files I read. - Do not review any GDD, do not spawn any sub-agent, do not run any template hook or script, 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 review-all-gdds folder into the agent's skills directory, in a folder named exactly "review-all-gdds", keeping its 8 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: review-all-gdds), the 8 files 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 spawns the template's game-designer agents, runs its review-scope script and resolves its settings through the yaml-helper hook), and that at use time it writes its report and any systems-index updates only after asking, with a silent session-state 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.