Game design option generation
Skill Stanestane/game-design-skills-bundle/game-design-option-generation
Generate multiple game design solution paths before committing to one direction. Use when a feature, live-ops idea, UX problem, economy issue, or design challenge feels too quickly narrowed, when a team is looping around one favorite answer, or when you need several credible options with tradeoffs instead of a single premature recommendation.From its SKILL.md
npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-option-generationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
SKILL.md
2.4 KB, 460 tokens by cl100k_base, as published. Nobody here has run it
Game Design Option Generation
Generate multiple credible ways forward before choosing one.
Use this skill to expand the solution space around a game design problem, feature pitch, or design goal. Keep the work practical. The aim is not random brainstorming. The aim is to produce several plausible options, clarify what makes them different, and expose tradeoffs early.
Read references/family-conventions.md when you need the shared conventions for this GROW-derived skill family.
What to produce
Generate:
- Problem framing - what needs solving
- Option set - at least 3 credible solution paths
- Tradeoff summary - player value, business value, cost, risk, strategic fit
- Recommendation - which path is strongest and why
Process
1. Frame the problem
Clarify:
- what outcome is desired
- what constraint or tension matters most
- what existing system context cannot be ignored
2. Generate multiple options
Always produce several options before deciding.
Use one or more of these lenses:
- Five-options - compare several existing ideas
- Obstacle - imagine the main blocker removed, then derive paths around it
- Ideal outcome - work backward from the best player-facing result
- Transformative reuse - adapt or extend what already exists
- Outside-the-box - deliberately include non-obvious options
3. Compare options
For each option, describe:
- summary
- strengths
- weaknesses
- likely player effect
- implementation burden
- strategic fit
4. Recommend a path
Choose the strongest option, or recommend a sequence such as test one now, hold one in reserve, discard the rest.
Response structure
Problem Framing
- ...
Options
- ...
- ...
- ...
Tradeoffs
- Option A: ...
- Option B: ...
- Option C: ...
Recommendation
- ...
Fast mode
- What problem are we actually solving?
- What are 3-5 plausible ways to solve it?
- Which one is best now, and why?
Working principle
Do not confuse the first decent answer with the best available direction.
What ships with it: 1 file
1.3 KB alongside SKILL.md
references/
- family-conventions.md1.3 KB