game-design-failure-loop-audit

Name: game-design-failure-loop-audit
Author: Stanestane

34stars3forks

How to install game-design-failure-loop-audit?

stanestane/game-design-skills-bundle/game-design-failure-loop-audit

$npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-failure-loop-audit

Installs into the current project.

Summary

Audit a game, feature, encounter structure, roguelite run, puzzle sequence, onboarding path, or progression gate through the lens of its failure loop: what happens after the player fails, what they learn, what they lose, and why they would or would not try again. Use when diagnos

Files · 1

View on GitHub

SKILL.md

1	# Game Design Failure Loop Audit
2
3	Audit what the game does after the player fails, and whether that loop produces learning, motivation, and retry energy instead of confusion, resentment, or collapse.
4
5	Use this skill when a design includes repeated failure states and the real question is not merely "is failure possible" but "what does failure do to the player over time?" The goal is to evaluate what the player loses, what they understand, what they retain, how fast they re-enter, and whether the failure loop makes them want another attempt.
6
7	Read `references/family-conventions.md` when you want the shared style, prioritization, and diagnosis rules for this game-design skill family.
8	Read `references/output-patterns.md` when you want the preferred recommendation and minimal-fix structure.
9
10	## Core principle
11
12	A good failure loop does not just punish. It converts defeat into renewed intention.
13
14	A strong failure loop usually provides:
15	- readable cause of failure
16	- meaningful lesson or hypothesis for next attempt
17	- tolerable cost relative to clarity
18	- manageable re-entry friction
19	- emotional permission to try again
20
21	A bad failure loop produces:
22	- confusion without learning
23	- punishment without agency
24	- downtime without anticipation
25	- repetition without adaptation
26	- shame, fatigue, or helplessness
27
28	## What to produce
29
30	Generate:
31	1. Failure loop summary - the current structure from failure to re-entry
32	2. Loss-learning-retry analysis - what the player loses, learns, and does next
33	3. Friction diagnosis - where punishment, delay, opacity, or humiliation break the loop
34	4. Motivation diagnosis - why players will retry, hesitate, or quit
35	5. Design implications - what to tune in cost, clarity, pacing, recovery, or support
36
37	## Process
38
39	### 1. Define the audit target
40	Clarify:
41	- what exact failure state or loop is being audited
42	- what player segment is most affected
43	- whether the focus is early churn, midgame frustration, endgame mastery, or broad retention
44
45	Write:
46	- Audit target
47	- Player segment
48	- Failure context
49
50	### 2. Reconstruct the full failure loop
51	Map the sequence:
52	- fail
53	- receive feedback
54	- pay consequence
55	- recover or reset
56	- prepare again
57	- retry or abandon
58
59	Ask:
60	- What happens immediately after failure?
61	- What is the player told or shown?
62	- What is lost?
63	- What remains?
64	- How long until the next meaningful attempt?
65	- What emotional state is the player likely in by then?
66
67	### 3. Audit loss, learning, and retention
68	Evaluate:
69	- what resources, progress, time, status, or opportunity are lost
70	- what information or understanding is gained
71	- what progression, meta-progress, or unlocked knowledge is retained
72	- whether the player can form a better next-attempt plan
73
74	Use this format:
75
76	\| Dimension \| Current state \| Effect on retry motivation \|
77	\|---\|---\|---\|
78	\| Loss \| ... \| ... \|
79	\| Learning \| ... \| ... \|
80	\| Retention \| ... \| ... \|
81	\| Re-entry speed \| ... \| ... \|
82
83	### 4. Diagnose re-entry friction
84	Look for:
85	- long dead time before the next real attempt
86	- tedious setup or replay of solved content
87	- unclear recovery path
88	- punishment that exceeds the educational value of the failure
89	- restart structures that encourage resignation rather than iteration
90
91	Ask:
92	- Is the retry fast enough?
93	- Is the player replaying meaningful challenge or just chores?
94	- Does the recovery path preserve tension or drain it?
95
96	### 5. Diagnose emotional effect
97	Check whether the failure loop tends to create:
98	- determination
99	- curiosity
100	- annoyance
101	- humiliation
102	- dread
103	- learned helplessness
104	- numb repetition
105
106	Name the most likely felt response and why.
107
108	### 6. Check fairness and attribution inside failure
109	Ask:
110	- does the player understand why they failed?
111	- does the punishment feel deserved?
112	- does the loop preserve a sense of control?
113	- does repeated failure harden into external blame?
114
115	If needed, call out connections to attribution, flow, or fairness problems without fully re-running those audits.
116
117	### 7. Identify failure-loop archetypes
118	Useful patterns include:
119	- learning loop - fast retry, high clarity, strong adaptation
120	- grindback loop - too much rebuild between real attempts
121	- shame loop - public or ego-threatening failure with weak learning
122	- attrition loop - death by repeated low-grade exhaustion
123	- helpless loop - repeated failure without better hypotheses
124	- mastery loop - hard punishment justified by high clarity and strong growth
125
126	Classify the current loop and say whether that shape suits the game.

StanestanePublisher · 59 listings

Preview

Stanestane/game-design-skills-bundle

# Game Design Failure Loop Audit

Audit what the game does after the player fails, and whether that loop produces learning, motivation, and retry energy instead of confusion, resentment, or coll

Use this skill when a design includes repeated failure states and the real question is not merely "is failure possible" but "what does failure do to the player

Read `references/family-conventions.md` when you want the shared style, prioritization, and diagnosis rules for this game-design skill family.

RepoStanestane/game-design-skills-bundle

License—

TypeSkills

CategoryDesign

UpdatedJun 2026

Repo stars34

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type

game-design-failure-loop-audit

34stars3forks

View on GitHub

How to install game-design-failure-loop-audit?

stanestane/game-design-skills-bundle/game-design-failure-loop-audit

$npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-failure-loop-audit

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Game Design Failure Loop Audit
2
3	Audit what the game does after the player fails, and whether that loop produces learning, motivation, and retry energy instead of confusion, resentment, or collapse.
4
5	Use this skill when a design includes repeated failure states and the real question is not merely "is failure possible" but "what does failure do to the player over time?" The goal is to evaluate what the player loses, what they understand, what they retain, how fast they re-enter, and whether the failure loop makes them want another attempt.
6
7	Read `references/family-conventions.md` when you want the shared style, prioritization, and diagnosis rules for this game-design skill family.
8	Read `references/output-patterns.md` when you want the preferred recommendation and minimal-fix structure.
9
10	## Core principle
11
12	A good failure loop does not just punish. It converts defeat into renewed intention.
13
14	A strong failure loop usually provides:
15	- readable cause of failure
16	- meaningful lesson or hypothesis for next attempt
17	- tolerable cost relative to clarity
18	- manageable re-entry friction
19	- emotional permission to try again
20
21	A bad failure loop produces:
22	- confusion without learning
23	- punishment without agency
24	- downtime without anticipation
25	- repetition without adaptation
26	- shame, fatigue, or helplessness
27
28	## What to produce
29
30	Generate:
31	1. Failure loop summary - the current structure from failure to re-entry
32	2. Loss-learning-retry analysis - what the player loses, learns, and does next
33	3. Friction diagnosis - where punishment, delay, opacity, or humiliation break the loop
34	4. Motivation diagnosis - why players will retry, hesitate, or quit
35	5. Design implications - what to tune in cost, clarity, pacing, recovery, or support
36
37	## Process
38
39	### 1. Define the audit target
40	Clarify:
41	- what exact failure state or loop is being audited
42	- what player segment is most affected
43	- whether the focus is early churn, midgame frustration, endgame mastery, or broad retention
44
45	Write:
46	- Audit target
47	- Player segment
48	- Failure context
49
50	### 2. Reconstruct the full failure loop
51	Map the sequence:
52	- fail
53	- receive feedback
54	- pay consequence
55	- recover or reset
56	- prepare again
57	- retry or abandon
58
59	Ask:
60	- What happens immediately after failure?
61	- What is the player told or shown?
62	- What is lost?
63	- What remains?
64	- How long until the next meaningful attempt?
65	- What emotional state is the player likely in by then?
66
67	### 3. Audit loss, learning, and retention
68	Evaluate:
69	- what resources, progress, time, status, or opportunity are lost
70	- what information or understanding is gained
71	- what progression, meta-progress, or unlocked knowledge is retained
72	- whether the player can form a better next-attempt plan
73
74	Use this format:
75
76	\| Dimension \| Current state \| Effect on retry motivation \|
77	\|---\|---\|---\|
78	\| Loss \| ... \| ... \|
79	\| Learning \| ... \| ... \|
80	\| Retention \| ... \| ... \|
81	\| Re-entry speed \| ... \| ... \|
82
83	### 4. Diagnose re-entry friction
84	Look for:
85	- long dead time before the next real attempt
86	- tedious setup or replay of solved content
87	- unclear recovery path
88	- punishment that exceeds the educational value of the failure
89	- restart structures that encourage resignation rather than iteration
90
91	Ask:
92	- Is the retry fast enough?
93	- Is the player replaying meaningful challenge or just chores?
94	- Does the recovery path preserve tension or drain it?
95
96	### 5. Diagnose emotional effect
97	Check whether the failure loop tends to create:
98	- determination
99	- curiosity
100	- annoyance
101	- humiliation
102	- dread
103	- learned helplessness
104	- numb repetition
105
106	Name the most likely felt response and why.
107
108	### 6. Check fairness and attribution inside failure
109	Ask:
110	- does the player understand why they failed?
111	- does the punishment feel deserved?
112	- does the loop preserve a sense of control?
113	- does repeated failure harden into external blame?
114
115	If needed, call out connections to attribution, flow, or fairness problems without fully re-running those audits.
116
117	### 7. Identify failure-loop archetypes
118	Useful patterns include:
119	- learning loop - fast retry, high clarity, strong adaptation
120	- grindback loop - too much rebuild between real attempts
121	- shame loop - public or ego-threatening failure with weak learning
122	- attrition loop - death by repeated low-grade exhaustion
123	- helpless loop - repeated failure without better hypotheses
124	- mastery loop - hard punishment justified by high clarity and strong growth
125
126	Classify the current loop and say whether that shape suits the game.

StanestanePublisher · 59 listings

Preview

Stanestane/game-design-skills-bundle

# Game Design Failure Loop Audit

Audit what the game does after the player fails, and whether that loop produces learning, motivation, and retry energy instead of confusion, resentment, or coll

Use this skill when a design includes repeated failure states and the real question is not merely "is failure possible" but "what does failure do to the player

Read `references/family-conventions.md` when you want the shared style, prioritization, and diagnosis rules for this game-design skill family.

RepoStanestane/game-design-skills-bundle

License—

TypeSkills

CategoryDesign

UpdatedJun 2026

Repo stars34

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type