game-design-zeigarnik-effect-audit

Name: game-design-zeigarnik-effect-audit
Author: Stanestane

34stars3forks

How to install game-design-zeigarnik-effect-audit?

stanestane/game-design-skills-bundle/game-design-zeigarnik-effect-audit

$npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-zeigarnik-effect-audit

Installs into the current project.

Summary

Audit a game, feature, task system, quest flow, event track, puzzle chain, progression layer, or return loop through the lens of the Zeigarnik effect: the tension created by incomplete, interrupted, or unresolved tasks. Use when evaluating whether a design creates healthy return

Files · 1

View on GitHub

SKILL.md

1	# Game Design Zeigarnik Effect Audit
2
3	Audit a design by asking how it uses unfinished business and whether that unfinishedness creates useful tension or just psychic clutter.
4
5	Use this skill when a feature depends on incomplete tasks, suspended goals, unresolved quests, unfinished collections, interrupted runs, dangling mysteries, near-complete progress bars, or other forms of cognitive open-loop tension. The goal is to evaluate whether the design creates healthy return pull, curiosity, and momentum, or whether it produces guilt, overwhelm, clutter, and coercive pressure.
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	Unfinished things stick in the mind.
13
14	In games, that can be powerful. An incomplete task can create:
15	- return motivation
16	- curiosity
17	- anticipation
18	- desire for closure
19	- mental continuity between sessions
20
21	But open loops become toxic when they create:
22	- obligation without excitement
23	- clutter without priority
24	- anxiety without clarity
25	- guilt without meaningful choice
26	- manipulative pressure to return
27
28	The point is not merely to leave things unfinished. The point is to leave the right things unfinished in the right way.
29
30	## What to produce
31
32	Generate:
33	1. Open-loop profile - what unresolved elements the design leaves active in the player's mind
34	2. Return-tension diagnosis - whether incompletion creates healthy pull or unhealthy pressure
35	3. Clarity and prioritization diagnosis - whether the player knows what is unfinished and why it matters
36	4. Clutter and coercion risks - where open loops become noise, guilt, or manipulative burden
37	5. Design actions - what to sharpen, resolve, stage, reduce, or frame differently
38
39	## Process
40
41	### 1. Define the audit target
42	Clarify:
43	- what exact system, flow, or experience slice is being audited
44	- what unresolved elements matter most
45	- whether the concern is retention, curiosity, task load, or psychological pressure
46
47	Write:
48	- Audit target
49	- Open-loop type
50	- Primary concern
51
52	### 2. Identify the unresolved loops
53	Look for things like:
54	- incomplete quests
55	- partial event tracks
56	- nearly finished collections
57	- dangling narrative mysteries
58	- interrupted crafting or building goals
59	- unresolved social obligations
60	- suspended runs or puzzle attempts
61	- pending claim states
62	- visible near-misses
63
64	Ask:
65	- what remains unfinished?
66	- what keeps that unfinishedness mentally active?
67	- is the loop explicit, implied, or ambient?
68
69	### 3. Classify the kind of tension being created
70	Useful categories include:
71	- curiosity tension
72	- completion tension
73	- competence tension
74	- social obligation tension
75	- reward anticipation tension
76	- scarcity/FOMO tension
77	- guilt/maintenance tension
78
79	Not all tension is equally healthy.
80
81	### 4. Audit clarity and closure path
82	Ask:
83	- does the player understand what is unresolved?
84	- do they know how to resume or resolve it?
85	- is the next step obvious enough to act on?
86	- is there one clean open loop or a pile of competing ones?
87	- does the system preserve meaningful stopping points, or does it always leave the player hanging messily?
88
89	### 5. Diagnose healthy versus unhealthy open loops
90	Healthy open loops tend to be:
91	- legible
92	- meaningful
93	- self-directed
94	- motivating
95	- finite enough to imagine closure
96
97	Unhealthy open loops tend to be:
98	- noisy
99	- coercive
100	- low-value
101	- ambiguous
102	- too numerous
103	- attached to shame or maintenance burden
104
105	Ask:
106	- does the player return because they want closure, or because they feel nagged?
107	- is the unfinishedness energizing or depleting?
108	- is the pressure chosen or imposed?
109
110	### 6. Check interaction with session structure
111	Ask:
112	- does the system give players safe stopping points?
113	- does it create a clear "one more thing" pull?
114	- does it overload session endings with too many unresolved hooks?
115	- does it preserve continuity between sessions without creating dread?
116
117	This is especially important for retention design and return loops.
118
119	### 7. Diagnose Zeigarnik failure patterns
120	Look for:
121	- too many simultaneous unfinished tasks
122	- near-completion bait with weak actual payoff
123	- open loops that matter only because the UI keeps nagging about them
124	- unresolved states with poor re-entry clarity
125	- social obligations that convert return into guilt
126	- cliffhangers without enough mea

StanestanePublisher · 59 listings

Preview

Stanestane/game-design-skills-bundle

# Game Design Zeigarnik Effect Audit

Audit a design by asking how it uses unfinished business and whether that unfinishedness creates useful tension or just psychic clutter.

Use this skill when a feature depends on incomplete tasks, suspended goals, unresolved quests, unfinished collections, interrupted runs, dangling mysteries, nea

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-zeigarnik-effect-audit

34stars3forks

View on GitHub

How to install game-design-zeigarnik-effect-audit?

stanestane/game-design-skills-bundle/game-design-zeigarnik-effect-audit

$npx -y skills add Stanestane/game-design-skills-bundle --skill game-design-zeigarnik-effect-audit

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Game Design Zeigarnik Effect Audit
2
3	Audit a design by asking how it uses unfinished business and whether that unfinishedness creates useful tension or just psychic clutter.
4
5	Use this skill when a feature depends on incomplete tasks, suspended goals, unresolved quests, unfinished collections, interrupted runs, dangling mysteries, near-complete progress bars, or other forms of cognitive open-loop tension. The goal is to evaluate whether the design creates healthy return pull, curiosity, and momentum, or whether it produces guilt, overwhelm, clutter, and coercive pressure.
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	Unfinished things stick in the mind.
13
14	In games, that can be powerful. An incomplete task can create:
15	- return motivation
16	- curiosity
17	- anticipation
18	- desire for closure
19	- mental continuity between sessions
20
21	But open loops become toxic when they create:
22	- obligation without excitement
23	- clutter without priority
24	- anxiety without clarity
25	- guilt without meaningful choice
26	- manipulative pressure to return
27
28	The point is not merely to leave things unfinished. The point is to leave the right things unfinished in the right way.
29
30	## What to produce
31
32	Generate:
33	1. Open-loop profile - what unresolved elements the design leaves active in the player's mind
34	2. Return-tension diagnosis - whether incompletion creates healthy pull or unhealthy pressure
35	3. Clarity and prioritization diagnosis - whether the player knows what is unfinished and why it matters
36	4. Clutter and coercion risks - where open loops become noise, guilt, or manipulative burden
37	5. Design actions - what to sharpen, resolve, stage, reduce, or frame differently
38
39	## Process
40
41	### 1. Define the audit target
42	Clarify:
43	- what exact system, flow, or experience slice is being audited
44	- what unresolved elements matter most
45	- whether the concern is retention, curiosity, task load, or psychological pressure
46
47	Write:
48	- Audit target
49	- Open-loop type
50	- Primary concern
51
52	### 2. Identify the unresolved loops
53	Look for things like:
54	- incomplete quests
55	- partial event tracks
56	- nearly finished collections
57	- dangling narrative mysteries
58	- interrupted crafting or building goals
59	- unresolved social obligations
60	- suspended runs or puzzle attempts
61	- pending claim states
62	- visible near-misses
63
64	Ask:
65	- what remains unfinished?
66	- what keeps that unfinishedness mentally active?
67	- is the loop explicit, implied, or ambient?
68
69	### 3. Classify the kind of tension being created
70	Useful categories include:
71	- curiosity tension
72	- completion tension
73	- competence tension
74	- social obligation tension
75	- reward anticipation tension
76	- scarcity/FOMO tension
77	- guilt/maintenance tension
78
79	Not all tension is equally healthy.
80
81	### 4. Audit clarity and closure path
82	Ask:
83	- does the player understand what is unresolved?
84	- do they know how to resume or resolve it?
85	- is the next step obvious enough to act on?
86	- is there one clean open loop or a pile of competing ones?
87	- does the system preserve meaningful stopping points, or does it always leave the player hanging messily?
88
89	### 5. Diagnose healthy versus unhealthy open loops
90	Healthy open loops tend to be:
91	- legible
92	- meaningful
93	- self-directed
94	- motivating
95	- finite enough to imagine closure
96
97	Unhealthy open loops tend to be:
98	- noisy
99	- coercive
100	- low-value
101	- ambiguous
102	- too numerous
103	- attached to shame or maintenance burden
104
105	Ask:
106	- does the player return because they want closure, or because they feel nagged?
107	- is the unfinishedness energizing or depleting?
108	- is the pressure chosen or imposed?
109
110	### 6. Check interaction with session structure
111	Ask:
112	- does the system give players safe stopping points?
113	- does it create a clear "one more thing" pull?
114	- does it overload session endings with too many unresolved hooks?
115	- does it preserve continuity between sessions without creating dread?
116
117	This is especially important for retention design and return loops.
118
119	### 7. Diagnose Zeigarnik failure patterns
120	Look for:
121	- too many simultaneous unfinished tasks
122	- near-completion bait with weak actual payoff
123	- open loops that matter only because the UI keeps nagging about them
124	- unresolved states with poor re-entry clarity
125	- social obligations that convert return into guilt
126	- cliffhangers without enough mea

StanestanePublisher · 59 listings

Preview

Stanestane/game-design-skills-bundle

# Game Design Zeigarnik Effect Audit

Audit a design by asking how it uses unfinished business and whether that unfinishedness creates useful tension or just psychic clutter.

Use this skill when a feature depends on incomplete tasks, suspended goals, unresolved quests, unfinished collections, interrupted runs, dangling mysteries, nea

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