scenario-map

Name: scenario-map
Author: Owl-Listener

82stars25forks

How to install scenario-map?

owl-listener/inclusive-design-skills/scenario-map

$npx -y skills add Owl-Listener/inclusive-design-skills --skill scenario-map

Installs into the current project.

Summary

Map inclusive usage scenarios across ability spectrums for a product or feature. Chains: ability-spectrum-mapping, situational-impairment-mapping, assistive-technology-scenarios. Use when planning test coverage, identifying accessibility gaps, or understanding how a feature perfo

Files · 1

View on GitHub

SKILL.md

1	# Map Inclusive Usage Scenarios
2
3	Generate a comprehensive map of how a product or feature is experienced
4	across different abilities, technologies, and contexts — surfacing
5	gaps before users find them.
6
7	## Process
8
9	### Step 1: Identify Core Tasks
10	List the 5–10 most important tasks for the product or feature.
11	Focus on the tasks that matter most to users — the ones where
12	failure means the product has failed.
13
14	### Step 2: Map the Ability Spectrum
15	Using ability-spectrum-mapping, for each core task, rate
16	performance across vision, hearing, motor, and cognitive spectrums.
17	Identify the breakpoints where each task degrades or fails.
18
19	### Step 3: Map Situational Contexts
20	Using situational-impairment-mapping, identify the realistic
21	contexts where users encounter your product and the impairments
22	those contexts create. Cross-reference with the ability spectrum
23	to find compounding effects.
24
25	### Step 4: Write Critical Scenarios
26	Using assistive-technology-scenarios, write detailed scenarios
27	for the highest-risk combinations: the tasks most likely to fail
28	for the users most likely to be affected.
29
30	Prioritise:
31	- Core tasks that fail at common ability levels
32	- Situational contexts that affect large user populations
33	- Combinations where multiple impairments compound
34
35	### Step 5: Identify Gaps and Priorities
36	Map all findings into a single view showing:
37	- Which tasks work for whom
38	- Where the breakpoints are
39	- Which fixes would include the most users
40
41	## Output
42
43	Deliver a scenario map containing:
44
45	1. Task × ability matrix — showing works / friction / fails for
46	each combination
47	2. Situational context overlay — which contexts compound which
48	ability barriers
49	3. Critical scenarios — detailed narratives for highest-risk
50	combinations
51	4. Gap analysis — where the product fails and for whom
52	5. Priority fixes — ranked by number of users unblocked and
53	severity of current failure

People who liked this also viewed

6 picks

Type

scenario-map

82stars25forks

View on GitHub

How to install scenario-map?

owl-listener/inclusive-design-skills/scenario-map

$npx -y skills add Owl-Listener/inclusive-design-skills --skill scenario-map

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Map Inclusive Usage Scenarios
2
3	Generate a comprehensive map of how a product or feature is experienced
4	across different abilities, technologies, and contexts — surfacing
5	gaps before users find them.
6
7	## Process
8
9	### Step 1: Identify Core Tasks
10	List the 5–10 most important tasks for the product or feature.
11	Focus on the tasks that matter most to users — the ones where
12	failure means the product has failed.
13
14	### Step 2: Map the Ability Spectrum
15	Using ability-spectrum-mapping, for each core task, rate
16	performance across vision, hearing, motor, and cognitive spectrums.
17	Identify the breakpoints where each task degrades or fails.
18
19	### Step 3: Map Situational Contexts
20	Using situational-impairment-mapping, identify the realistic
21	contexts where users encounter your product and the impairments
22	those contexts create. Cross-reference with the ability spectrum
23	to find compounding effects.
24
25	### Step 4: Write Critical Scenarios
26	Using assistive-technology-scenarios, write detailed scenarios
27	for the highest-risk combinations: the tasks most likely to fail
28	for the users most likely to be affected.
29
30	Prioritise:
31	- Core tasks that fail at common ability levels
32	- Situational contexts that affect large user populations
33	- Combinations where multiple impairments compound
34
35	### Step 5: Identify Gaps and Priorities
36	Map all findings into a single view showing:
37	- Which tasks work for whom
38	- Where the breakpoints are
39	- Which fixes would include the most users
40
41	## Output
42
43	Deliver a scenario map containing:
44
45	1. Task × ability matrix — showing works / friction / fails for
46	each combination
47	2. Situational context overlay — which contexts compound which
48	ability barriers
49	3. Critical scenarios — detailed narratives for highest-risk
50	combinations
51	4. Gap analysis — where the product fails and for whom
52	5. Priority fixes — ranked by number of users unblocked and
53	severity of current failure

People who liked this also viewed

6 picks

Type