Game Design Brainstorm Methods

Apply established brainstorming and ideation methodologies to game design problems, features, systems, UX flows, live-ops ideas, content concepts, and stuck...

Security Scan

This is an instruction-only brainstorming skill whose requested resources and runtime instructions match its stated purpose and contain no obvious surprises.

Purpose & Capability

Name, description, and included reference files all describe brainstorming/ideation methods; there are no unrelated binaries, credentials, or install steps requested.

Instruction Scope

SKILL.md and the two reference docs strictly describe how to choose and run ideation methods and what output to produce; they reference only local files and method structures and do not instruct reading unrelated files, accessing external endpoints, or exfiltrating data.

Install Mechanism

No install spec or code files that would write or execute external artifacts are present; the skill is instruction-only, which is the lowest install risk.

Credentials

The skill requires no environment variables, credentials, or config paths — consistent with a purely procedural brainstorming tool.

Persistence & Privilege

Flags show always:false and default autonomous invocation allowed (platform default). The skill does not request persistent system privileges or modify other skills.

Assessment

This skill appears coherent and low-risk because it only contains textual instructions and internal reference documents. Before using it, avoid pasting sensitive IP or unreleased game assets into prompts (the model’s outputs may be stored or logged by your platform). Review generated ideas for accuracy and feasibility — the skill simulates workshop formats and can hallucinate specifics. If you need to share confidential design details, consider sanitizing them or running the skill in a controlled environment. Finally, note the source/homepage is unknown; if provenance matters, seek a known author or equivalent vetted resource.

Use named brainstorming methods, not generic idea spray.

This skill helps choose and run a well-known ideation methodology that fits the design problem. The goal is not to mention frameworks for show. The goal is to use the right method to unlock better game design options, surface hidden assumptions, and produce a practical shortlist worth exploring next.

Read references/method-selection.md when choosing a method. Read references/method-patterns.md when you need the exact structure for a method output.

What to produce

Produce:

1. Problem frame - what the team is trying to solve
2. Method choice - which brainstorming method is best and why
3. Method run - the actual brainstorm output in that method's format
4. Idea clusters - themes, repeated patterns, or promising directions
5. Shortlist - strongest candidates to pursue next
6. Next move - recommendation, prototype, or follow-up question

Process

1. Frame the ideation problem

Clarify:

• what design problem, feature, or system is under discussion
• whether the need is divergence, reframing, critique, or narrowing
• what constraints matter most
• whether the user wants novelty, structure, speed, or alignment

2. Choose the right method

Pick one primary method. Use a second method only when it adds clear value.

Typical fits:

• SCAMPER - improve or mutate an existing feature
• How Might We - turn fuzzy problems into opportunity prompts
• Crazy 8s - force fast variation and volume
• Six Thinking Hats - structure discussion across multiple lenses
• Brainwriting 6-3-5 - generate many ideas without one dominant voice
• Worst Possible Idea - break fixation by inverting bad ideas into useful principles
• Forced connections - inject novelty through random or adjacent stimuli
• Lotus Blossom - expand one central idea into adjacent branches
• Morphological matrix - combine dimensions systematically into new concepts

3. Run the method properly

Do not collapse the method into generic bullets. Preserve the logic of the method. For example:

• SCAMPER should actually walk through substitute, combine, adapt, modify, put to other use, eliminate, reverse/rearrange
• Six Thinking Hats should clearly separate hat modes
• Brainwriting should show rounds, seeds, or parallel idea contributions
• Morphological matrix should define dimensions before combining them

4. Extract the design value

After the method run, identify:

• repeated themes
• strongest directions
• strange but interesting outliers
• weak ideas worth discarding
• what should be prototyped, discussed, or parked

5. Convert brainstorm into action

End with one of these:

• best 3 candidates
• one recommended direction and why
• next prototype question
• follow-up method if the first method created useful ambiguity but not enough convergence

Response structure

Problem Frame

• ...

Chosen Method

• Method: ...
• Why this method fits: ...

Method Run

• ...

Idea Clusters

• ...

Strongest Candidates

1. ...
2. ...
3. ...

Recommended Next Move

• ...

Fast mode

• What kind of ideation problem is this?
• Which method fits best?
• Run that method clearly.
• Pull out the 3 strongest design directions.
• Recommend what to do next.

Working principle

Different brainstorming problems need different tools. Do not default to freeform ideation when a specific method would produce better thinking.