
scenario-map
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 performs across diverse users.
- Installs
- 73
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/inclusive-design-skills --skill scenario-map- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads scenario-map automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Map Inclusive Usage Scenarios
Generate a comprehensive map of how a product or feature is experienced across different abilities, technologies, and contexts — surfacing gaps before users find them.
Process
Step 1: Identify Core Tasks
List the 5–10 most important tasks for the product or feature. Focus on the tasks that matter most to users — the ones where failure means the product has failed.
Step 2: Map the Ability Spectrum
Using ability-spectrum-mapping, for each core task, rate performance across vision, hearing, motor, and cognitive spectrums. Identify the breakpoints where each task degrades or fails.
Step 3: Map Situational Contexts
Using situational-impairment-mapping, identify the realistic contexts where users encounter your product and the impairments those contexts create. Cross-reference with the ability spectrum to find compounding effects.
Step 4: Write Critical Scenarios
Using assistive-technology-scenarios, write detailed scenarios for the highest-risk combinations: the tasks most likely to fail for the users most likely to be affected.
Prioritise:
- Core tasks that fail at common ability levels
- Situational contexts that affect large user populations
- Combinations where multiple impairments compound
Step 5: Identify Gaps and Priorities
Map all findings into a single view showing:
- Which tasks work for whom
- Where the breakpoints are
- Which fixes would include the most users
Output
Deliver a scenario map containing:
- Task × ability matrix — showing works / friction / fails for each combination
- Situational context overlay — which contexts compound which ability barriers
- Critical scenarios — detailed narratives for highest-risk combinations
- Gap analysis — where the product fails and for whom
- Priority fixes — ranked by number of users unblocked and severity of current failure
FAQ
What does the scenario-map skill do?
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 performs across diverse users.
How do I install scenario-map?
Run npx skills add https://github.com/owl-listener/inclusive-design-skills --skill scenario-map in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/scenario-map/ (personal) or .claude/skills/scenario-map/ (project).
Which AI agents can use scenario-map?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is scenario-map safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains scenario-map?
It is published by owl-listener in owl-listener/inclusive-design-skills. It has 73 recorded installs.
More from owl-listener/inclusive-design-skills
plain-language-design
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
keyboard-navigation
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
cognitive-load-assessment
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
responsive-review
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
user-preference-respect
owl-listener/inclusive-design-skills
Design interfaces that detect and respond to system-level user preferences. Use when implementing dark mode, reduced motion, high contrast, text scaling, or any user preference that affects how the interface renders. Triggers on: user preference, system preference, prefers-reduced-motion, prefers-contrast, prefers-color-scheme, forced-colors, media query, user settings, system settings, accessibility settings, OS settings.
error-prevention-recovery
owl-listener/inclusive-design-skills
Open the skill to read its SKILL.md instructions.
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work