game-design-ideal-outcome-backcasting

Name: game-design-ideal-outcome-backcasting
Author: Stanestane

34stars3forks

How to install game-design-ideal-outcome-backcasting?

stanestane/game-design-skills-bundle/game-design-ideal-outcome-backcasting

$npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-ideal-outcome-backcasting

Installs into the current project.

Summary

Start from the ideal player-facing result and work backward to the design steps, systems, and decisions required to reach it. Use when a team knows the kind of experience it wants but not how to structure the path there, when redesigning a feature around a stronger destination, o

Files · 1

View on GitHub

SKILL.md

1	# Game Design Ideal Outcome Backcasting
2
3	Start from the ideal future and work backward.
4
5	Use this skill when the end-state is easier to imagine than the path to reach it. Treat the ideal outcome as a design tool, not a fantasy wish list. The aim is to define the best believable player-facing result, then retrace the steps needed to make it real.
6
7	Read `references/family-conventions.md` when you need the shared conventions for this GROW-derived skill family.
8
9	## What to produce
10
11	Generate:
12	1. Ideal outcome - the best believable player-facing result
13	2. Required conditions - what must be true for that result to exist
14	3. Backward path - the enabling steps, systems, and decisions
15	4. Near-term priorities - what must happen first
16
17	## Process
18
19	### 1. Describe the ideal future
20	Clarify:
21	- what the player experience looks and feels like
22	- what success looks like in the feature or system
23	- what makes this version meaningfully better than the current one
24
25	### 2. Identify enabling conditions
26	Ask:
27	- what must exist for this outcome to work
28	- what systems, UX, content, or support layers are required
29	- what assumptions must hold true
30
31	### 3. Work backward
32	Retrace the path from the ideal state to the current state.
33	List:
34	- key milestones
35	- prerequisite systems
36	- sequencing dependencies
37	- learnings or tests needed before commitment
38
39	### 4. Distill immediate priorities
40	Separate:
41	- what must happen now
42	- what can wait
43	- what should be prototyped or validated first
44
45	## Response structure
46
47	### Ideal Outcome
48	- ...
49
50	### Required Conditions
51	- ...
52
53	### Backward Path
54	1. ...
55	2. ...
56	3. ...
57
58	### Immediate Priorities
59	- ...
60
61	## Fast mode
62	- What does the best believable version look like?
63	- What would need to be true for that version to work?
64	- What are the first steps backward from that destination?
65
66	## Working principle
67
68	A clearer destination makes the path easier to design.

People who liked this also viewed

6 picks

Type

game-design-ideal-outcome-backcasting

34stars3forks

View on GitHub

How to install game-design-ideal-outcome-backcasting?

stanestane/game-design-skills-bundle/game-design-ideal-outcome-backcasting

$npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-ideal-outcome-backcasting

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Game Design Ideal Outcome Backcasting
2
3	Start from the ideal future and work backward.
4
5	Use this skill when the end-state is easier to imagine than the path to reach it. Treat the ideal outcome as a design tool, not a fantasy wish list. The aim is to define the best believable player-facing result, then retrace the steps needed to make it real.
6
7	Read `references/family-conventions.md` when you need the shared conventions for this GROW-derived skill family.
8
9	## What to produce
10
11	Generate:
12	1. Ideal outcome - the best believable player-facing result
13	2. Required conditions - what must be true for that result to exist
14	3. Backward path - the enabling steps, systems, and decisions
15	4. Near-term priorities - what must happen first
16
17	## Process
18
19	### 1. Describe the ideal future
20	Clarify:
21	- what the player experience looks and feels like
22	- what success looks like in the feature or system
23	- what makes this version meaningfully better than the current one
24
25	### 2. Identify enabling conditions
26	Ask:
27	- what must exist for this outcome to work
28	- what systems, UX, content, or support layers are required
29	- what assumptions must hold true
30
31	### 3. Work backward
32	Retrace the path from the ideal state to the current state.
33	List:
34	- key milestones
35	- prerequisite systems
36	- sequencing dependencies
37	- learnings or tests needed before commitment
38
39	### 4. Distill immediate priorities
40	Separate:
41	- what must happen now
42	- what can wait
43	- what should be prototyped or validated first
44
45	## Response structure
46
47	### Ideal Outcome
48	- ...
49
50	### Required Conditions
51	- ...
52
53	### Backward Path
54	1. ...
55	2. ...
56	3. ...
57
58	### Immediate Priorities
59	- ...
60
61	## Fast mode
62	- What does the best believable version look like?
63	- What would need to be true for that version to work?
64	- What are the first steps backward from that destination?
65
66	## Working principle
67
68	A clearer destination makes the path easier to design.

People who liked this also viewed

6 picks

Type