game-design-grow-design

Name: game-design-grow-design
Author: Stanestane

34stars3forks

How to install game-design-grow-design?

stanestane/game-design-skills-bundle/game-design-grow-design

$npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-grow-design

Installs into the current project.

Summary

Evaluate game features, feature pitches, live-ops ideas, UX changes, economy changes, roadmap choices, retention initiatives, monetization initiatives, and ambiguous design problems using the GROW model: Goal, Reality, Options, Will. Use when a team needs structure, clearer decis

Files · 1

View on GitHub

SKILL.md

1	# Game Design GROW Design
2
3	Use the GROW model to turn vague game design conversations into a structured decision flow:
4
5	Goal -> Reality -> Options -> Will
6
7	Use this skill when a team has ideas, concerns, and opinions, but not enough shared structure to reach a decision. Keep the framework practical, explicit, and usable by teams that need help clarifying what they want, what is true right now, what they could do, and what they should commit to next.
8
9	## What to produce
10
11	Generate a structured decision pass with these outputs:
12
13	1. Goal - a concise statement of the intended outcome and success criteria
14	2. Reality - the current state, constraints, dependencies, and unknowns
15	3. Options - multiple credible paths, not just one preferred answer
16	4. Will - a recommendation, immediate next steps, and validation needs
17
18	## Process
19
20	### 1. Goal
21
22	Clarify what the team is trying to achieve.
23
24	Ask:
25	- What player problem does this solve?
26	- What player behavior should change?
27	- What business or product goal does this support?
28	- How should this fit existing game loops and systems?
29	- What does success look like in player terms?
30	- What does success look like in KPI terms?
31	- What are the quality constraints?
32	- What is the release window or decision horizon?
33
34	Use a SMART-style structure:
35	- Specific - clearly describe the feature intent
36	- Measurable - define KPIs or evaluation signals
37	- Attainable - keep the goal feasible within team and technical limits
38	- Relevant - connect the idea to game strategy and product priorities
39	- Time-boxed - align it to a release, milestone, or decision window
40
41	Write:
42	- Goal statement
43	- Success criteria
44	- Key constraints
45
46	Suggested format:
47
48	Goal statement
49	We want to [player/business outcome] by introducing or changing [feature/system], measured by [metrics/signals], within [timeframe].
50
51	### 2. Reality
52
53	Describe what is true right now.
54
55	Build a grounded picture of the current situation.
56
57	Ask:
58	- What is the current player experience?
59	- What already exists that overlaps with this idea?
60	- Which systems would this touch?
61	- What infrastructure, tools, or content pipelines already exist?
62	- What are the open design questions?
63	- What resourcing constraints exist?
64	- What tech, UX, or economy limitations exist?
65	- What assumptions are currently unverified?
66	- Which comparable features already exist in this game or similar games?
67	- What data or prior learnings matter?
68
69	Useful categories:
70	- Game state - existing systems, loops, progression context
71	- Player state - motivations, friction, expectations
72	- Business state - targets, roadmap role, cannibalization risk
73	- Production state - scope, dependencies, tech constraints
74	- Evidence state - telemetry, benchmarks, prior experiments, team learnings
75
76	Write:
77	- Current state
78	- Constraints
79	- Unknowns
80	- Dependencies
81
82	Suggested format:
83
84	Reality summary
85	Current state: ...
86	Constraints: ...
87	Unknowns: ...
88	Dependencies: ...
89
90	### 3. Options
91
92	Generate multiple credible solution paths before recommending anything.
93
94	General rule: always produce several options, even when one path seems obvious.
95
96	#### Option-generation methods
97
98	Choose one or combine several:
99
100	A. Five-options approach
101	Use when several candidate solutions already exist.
102	- list at least 3-5 approaches
103	- define pros and cons for each
104	- compare expected impact and implementation cost
105	- identify the fastest testable version
106
107	B. Obstacle approach
108	Use when the team is blocked by one obvious problem.
109	- name the roadblock clearly
110	- imagine it removed
111	- describe the resulting design space
112	- derive workaround paths
113
114	C. Ideal-outcome approach
115	Use when direction is unclear but the end state is clear.
116	- describe the ideal player experience
117	- work backwards from that state
118	- identify enabling components and milestones
119
120	D. Transformative approach
121	Use when building on existing systems is likely better than inventing from scratch.
122	- identify reusable systems, UI, content pipelines, currencies, or loops
123	- ask what can be tuned, recombined, or extended
124	- prefer leverage over novelty where appropriate
125
126	E. Thinking outside the box
127	Use when the problem is understood but no satisfying approach exists.
128	- brainstorm without commitment
129	- deliberately include non-obvious approaches
130	- separate idea generation from evaluation
131
132	#### Evaluate each option
133
134	For each option, score:
135	- Player value (1-5)
136	- Business value (1-5)
137	- Implementation cost (1-5

People who liked this also viewed

6 picks

Type

game-design-grow-design

34stars3forks

View on GitHub

How to install game-design-grow-design?

stanestane/game-design-skills-bundle/game-design-grow-design

$npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-grow-design

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Game Design GROW Design
2
3	Use the GROW model to turn vague game design conversations into a structured decision flow:
4
5	Goal -> Reality -> Options -> Will
6
7	Use this skill when a team has ideas, concerns, and opinions, but not enough shared structure to reach a decision. Keep the framework practical, explicit, and usable by teams that need help clarifying what they want, what is true right now, what they could do, and what they should commit to next.
8
9	## What to produce
10
11	Generate a structured decision pass with these outputs:
12
13	1. Goal - a concise statement of the intended outcome and success criteria
14	2. Reality - the current state, constraints, dependencies, and unknowns
15	3. Options - multiple credible paths, not just one preferred answer
16	4. Will - a recommendation, immediate next steps, and validation needs
17
18	## Process
19
20	### 1. Goal
21
22	Clarify what the team is trying to achieve.
23
24	Ask:
25	- What player problem does this solve?
26	- What player behavior should change?
27	- What business or product goal does this support?
28	- How should this fit existing game loops and systems?
29	- What does success look like in player terms?
30	- What does success look like in KPI terms?
31	- What are the quality constraints?
32	- What is the release window or decision horizon?
33
34	Use a SMART-style structure:
35	- Specific - clearly describe the feature intent
36	- Measurable - define KPIs or evaluation signals
37	- Attainable - keep the goal feasible within team and technical limits
38	- Relevant - connect the idea to game strategy and product priorities
39	- Time-boxed - align it to a release, milestone, or decision window
40
41	Write:
42	- Goal statement
43	- Success criteria
44	- Key constraints
45
46	Suggested format:
47
48	Goal statement
49	We want to [player/business outcome] by introducing or changing [feature/system], measured by [metrics/signals], within [timeframe].
50
51	### 2. Reality
52
53	Describe what is true right now.
54
55	Build a grounded picture of the current situation.
56
57	Ask:
58	- What is the current player experience?
59	- What already exists that overlaps with this idea?
60	- Which systems would this touch?
61	- What infrastructure, tools, or content pipelines already exist?
62	- What are the open design questions?
63	- What resourcing constraints exist?
64	- What tech, UX, or economy limitations exist?
65	- What assumptions are currently unverified?
66	- Which comparable features already exist in this game or similar games?
67	- What data or prior learnings matter?
68
69	Useful categories:
70	- Game state - existing systems, loops, progression context
71	- Player state - motivations, friction, expectations
72	- Business state - targets, roadmap role, cannibalization risk
73	- Production state - scope, dependencies, tech constraints
74	- Evidence state - telemetry, benchmarks, prior experiments, team learnings
75
76	Write:
77	- Current state
78	- Constraints
79	- Unknowns
80	- Dependencies
81
82	Suggested format:
83
84	Reality summary
85	Current state: ...
86	Constraints: ...
87	Unknowns: ...
88	Dependencies: ...
89
90	### 3. Options
91
92	Generate multiple credible solution paths before recommending anything.
93
94	General rule: always produce several options, even when one path seems obvious.
95
96	#### Option-generation methods
97
98	Choose one or combine several:
99
100	A. Five-options approach
101	Use when several candidate solutions already exist.
102	- list at least 3-5 approaches
103	- define pros and cons for each
104	- compare expected impact and implementation cost
105	- identify the fastest testable version
106
107	B. Obstacle approach
108	Use when the team is blocked by one obvious problem.
109	- name the roadblock clearly
110	- imagine it removed
111	- describe the resulting design space
112	- derive workaround paths
113
114	C. Ideal-outcome approach
115	Use when direction is unclear but the end state is clear.
116	- describe the ideal player experience
117	- work backwards from that state
118	- identify enabling components and milestones
119
120	D. Transformative approach
121	Use when building on existing systems is likely better than inventing from scratch.
122	- identify reusable systems, UI, content pipelines, currencies, or loops
123	- ask what can be tuned, recombined, or extended
124	- prefer leverage over novelty where appropriate
125
126	E. Thinking outside the box
127	Use when the problem is understood but no satisfying approach exists.
128	- brainstorm without commitment
129	- deliberately include non-obvious approaches
130	- separate idea generation from evaluation
131
132	#### Evaluate each option
133
134	For each option, score:
135	- Player value (1-5)
136	- Business value (1-5)
137	- Implementation cost (1-5

People who liked this also viewed

6 picks

Type