Brainstorm

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 "Brainstorm" for me. It is the Game Studios concept-finding skill. In the minimal workflow it runs the Lean Brief flow in SKILL.md: it proposes 2 or 3 one-line concepts, fills a one-page brief in conversation (working title, pitch, core loop, player goal and fail state, an MVP list it pushes back on past 7 items, out-of-scope list, build order), shows the brief in full and writes design/game-brief.md only on an explicit yes to its own write question. In the standard or full workflow it instead reads and follows references/full-concept.md: creative discovery, three generated concepts, core loop, pillars and anti-pillars, player types, scope and feasibility, then design/gdd/game-concept.md written the same ask-first way; full review mode hands pillar, visual, feasibility and scope gates to the creative-director, art-director, technical-director and producer template agents. It never picks an engine for the user, and its frontmatter allowed tools include WebSearch. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/brainstorm/ folder at the pinned commit: 2 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/brainstorm/ 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 fa665de84aea3834111c981e919ac166f0a8400764c4c23d579d9a929c0539b6 - references/full-concept.md: SHA-256 ce34add9f9eb81de45a955d47bda252091a3d8fd6a6c390ee2c09d277f0e1dfa 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 2 files: SKILL.md plus references/full-concept.md, the full concept flow the SKILL.md reads and follows at the standard and full workflow tiers (the minimal tier never loads it). Nothing in the folder is a program; the reference file is instructions the skill reads 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 read or modified. - Integrated-system reality, from the files: at use time the skill resolves studio configuration by running the template's hooks/yaml-helper.sh (keys review_mode, automation, docs.density, workflow), reads the template's .claude/docs/ mode and gate documents and its .claude/docs/templates/ brief and concept templates, reads project.yaml for the engine name, and in full review mode spawns the template's creative-director, art-director, technical-director and producer agents — files and agents that live outside this skill's folder and are absent in a standalone install, so parts of it cannot run outside the full template. Its allowed tools also include WebSearch, so at use time it may search the web; the workflow text itself works from the conversation and the template's files. - At use time it writes only after asking, and only in my own project: design/game-brief.md at the minimal tier or design/gdd/game-concept.md at the standard/full tiers, each on an explicit yes to the skill's own write question. No account, key or payment is named in the files I read; the one outward capability in its allowed tools is WebSearch, named in the point above. - Do not brainstorm any concept, 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 brainstorm folder into the agent's skills directory, in a folder named exactly "brainstorm", keeping its 2 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: brainstorm), the 2 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 resolves its settings through the template's yaml-helper hook and reads the template's docs and templates), and that using it writes a game brief or a game concept document in my project only after I explicitly say yes). 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.