Game Concept Brainstorm

Turn a vague game idea into a sharp fantasy, design pillars, player verbs, and acceptance bar before implementation begins. This is the proper “brainstorm” s...

Security Scan

The skill is an instruction-only brainstorming helper that only requires local file read/write (to produce docs) and references companion skills — its declared requirements and instructions match its stated purpose.

Purpose & Capability

Name/description (game concept brainstorming) aligns with what the bundle contains: templates, examples, and instructions to produce concept and requirements docs. Declared dependencies (companion skills) are related to the workflow and are reasonable.

Instruction Scope

SKILL.md limits behavior to restating fantasy, locking design pillars, separating must-haves/experiments, and writing outputs to docs using the provided template. It suggests file read/write access for best results, which is coherent with the deliverables; there are no instructions to access unrelated files, credentials, or external endpoints.

Install Mechanism

No install spec and no code files — instruction-only skill. Nothing is downloaded or executed on install, so there is minimal install risk.

Credentials

No environment variables, credentials, or config paths are requested. The only resource the skill reasonably needs is filesystem access to write the deliverable docs and to read the shared template included in the bundle.

Persistence & Privilege

always is false and the skill does not request special persistent privileges or to modify other skills. The default allowance for agent invocation is unchanged (normal platform behavior).

Assessment

This bundle appears coherent and low-risk: it is an instruction-only brainstorming helper that writes documentation using the included template and references companion skills. Before installing, consider: (1) the agent may need permission to read/write files in your workspace — run it in an isolated project folder if you want to limit scope; (2) companion skills listed are separate bundles—install or review them if you plan to chain workflows; (3) no credentials or network endpoints are requested by this bundle, but always review any companion skills for extra requirements; (4) if you prefer to prevent the agent from invoking the skill autonomously, adjust the agent's skill invocation settings (disable-model-invocation) on your platform.

Goal

Increase build success by locking the game fantasy before architecture or implementation.

Deliverables

• docs/game-studio/concept-brainstorm.md
• docs/game-studio/requirements.md

Use ./shared/templates/concept-brainstorm.md.

Use when

• the request is exciting but blurry
• the user asks for “make it good” or “make it fun”
• the team needs to protect the core fantasy from being flattened during implementation

Workflow

1. Restate the player fantasy in one sentence.
2. Lock the primary verb, the reward loop, and the first 30-second promise.
3. Define 3-4 design pillars.
4. Separate must-haves from experiments.
5. Prefer decisive defaults over endless questions.
6. Feed the result into game-requirements-brainstorm, game-scope-profile, and game-ux-flow-designer.

Important

This is not for random ideation. It is for increasing the chance that the first serious build actually feels like the intended game.