Agent skill

Inclusive User Stories

by Owl-Listener in Owl-Listener/inclusive-design-skills

Write user stories that account for disability and diverse abilities from the start.

MITAuto-check passedProduct & Project Management

Install Inclusive User Stories

skills CLI
$ npx skills add Owl-Listener/inclusive-design-skills --skill inclusive-user-stories -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Owl-Listener/inclusive-design-skills inclusive-user-stories --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/inclusive-personas/skills/inclusive-user-stories .claude/skills/inclusive-user-stories && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
inclusive-user-stories
GitHub stars
105
Token cost
~919 tokens
SKILL.md length
492 words
Files
1
Skills in repo
55
Repo updated
First seen
Licence
MIT

At a glance

Write user stories that account for disability and diverse abilities from the start.

  • Works in 4 steps: Read each story and ask: who does this… → Check acceptance criteria for keyboard,… → Flag any story that assumes a single… → …
  • Writing user stories
  • SKILL.md covers The Problem, The Fix, Story Structure and Patterns for Common Stories, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Inclusive User Stories is an agent skill from Owl-Listener/inclusive-design-skills. Write user stories that account for disability and diverse abilities from the start. Use when writing user stories, acceptance criteria, jobs to be done, or requirements. Triggers on: user story, user stories, acceptance criteria, jobs to be done, JTBD, requirements, as a user I want, definition of done, story writing.

Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering User stories. The repository describes itself as: Inclusive design skills for AI coding agents — from cognitive accessibility to adaptive interfaces, inclusive research, and accessibility decision-making. The licence is MIT.

When your agent uses it

  • Writing user stories
  • Acceptance criteria
  • Jobs to be done
  • As a user I want

Example prompts

  • “/inclusive-user-stories”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Read each story and ask: who does this exclude?
  2. Check acceptance criteria for keyboard, screen reader, visual,
  3. Flag any story that assumes a single input method or sense
  4. Add missing criteria — don't create separate stories

What it can do on your machine

Read from SKILL.md and the folder at commit 6e0740f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Inclusive User Stories loads about 919 tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 492 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
When it runs · the whole SKILL.md, loaded when a task matches
~919

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Owl-Listener/inclusive-design-skills at commit 6e0740f, republished under its MIT licence (© Owl-Listener). 492 words, ~919 tokens.

Download SKILL.mdSave it as .claude/skills/inclusive-user-stories/SKILL.md (or your agent's skills folder).
name
inclusive-user-stories
description
Write user stories that account for disability and diverse abilities from the start. Use when writing user stories, acceptance criteria, jobs to be done, or requirements. Triggers on: user story, user stories, acceptance criteria, jobs to be done, JTBD, requirements, as a user I want, definition of done, story writing.

Inclusive User Stories

Write user stories where accessibility is part of the acceptance criteria from the start — not added later as a separate ticket.

The Problem

Most user stories are written as: "As a user, I want to filter search results so I can find what I need."

This assumes a user who can see the filters, click small targets, read the labels, and process the results visually. It silently excludes anyone who interacts differently.

The Fix

Don't write separate "accessibility stories." Build inclusion into every story's acceptance criteria.

Story Structure

The Story

Keep the standard format: "As a [user], I want to [action] so that [outcome]."

But be specific about the user when it matters:

  • "As a keyboard-only user, I want to filter results using arrow keys and Enter so that I can narrow my search without a mouse."
  • "As a screen reader user, I want filter changes to be announced so that I know the results have updated."
Inclusive Acceptance Criteria

For every user story, add these checks to the acceptance criteria:

Keyboard:

  • Feature is fully operable with keyboard alone
  • Focus order is logical
  • Focus is visible on every interactive element

Screen reader:

  • All controls have accessible names
  • State changes are announced
  • Dynamic content updates use aria-live

Visual:

  • Information is not conveyed by colour alone
  • Text meets minimum contrast (4.5:1 for normal, 3:1 for large)
  • Content is readable at 200% zoom

Motor:

  • Touch targets are at least 44×44px
  • No time-dependent interactions without alternatives
  • No precision-dependent interactions without alternatives

Cognitive:

  • Instructions are in plain language
  • Error messages explain what to do, not just what went wrong
  • User can undo or recover from mistakes

Patterns for Common Stories

Show full SKILL.md (214 more words)Show less
"As a user, I want to complete a form"

Add:

  • Labels are visible and associated with fields
  • Required fields are indicated visually and programmatically
  • Errors appear inline next to the field, not just in a banner
  • Form can be completed with keyboard, touch, or voice
"As a user, I want to view a dashboard"

Add:

  • Data is not conveyed by colour alone (patterns, labels, values)
  • Charts have text summaries
  • Dashboard is navigable by keyboard with logical tab order
  • Key metrics are announced to screen readers
"As a user, I want to receive a notification"

Add:

  • Notification is visual AND programmatically announced
  • User can control notification preferences
  • Notification does not disappear before it can be read
  • Notification does not block other interactions

How to Audit Existing Stories

  1. Read each story and ask: who does this exclude?
  2. Check acceptance criteria for keyboard, screen reader, visual, motor, and cognitive requirements
  3. Flag any story that assumes a single input method or sense
  4. Add missing criteria — don't create separate stories

Assessment Questions

  1. Do acceptance criteria include keyboard, screen reader, and cognitive requirements?
  2. Are accessibility criteria part of the definition of done?
  3. Has each story been checked for assumptions about ability?
  4. Are there any stories that only work for one input method?

© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in inclusive-personas/skills/inclusive-user-stories of Owl-Listener/inclusive-design-skills.

Open the folder on GitHubat commit 6e0740f

Compare with similar skills

Inclusive User Stories next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Inclusive User Stories compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Inclusive User Stories this skillOwl-Listener/inclusive-design-skills105—~919Automated safety check: PassMIT
User Story Writerdeanpeters/Product-Manager-Skills7.2k2 repos~2.9kAutomated safety check: PassCustom licence
Ralph Tui Create Beadssubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT
Agile Product Owneralirezarezvani/claude-skills28k3 repos~3.2kAutomated safety check: PassMIT
Ralph Tui Create Beads Rustsubsy/ralph-tui2.5k1 repos~2.8kAutomated safety check: PassMIT
To Specbestofjs/bestofjs3.1k21 repos~757Automated safety check: PassMIT

Similar skills

  • User Story Writer

    deanpeters/Product-Manager-Skills

    Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.

    7.2k GitHub starsUsed in 2 repos~2.9k tokens
    Product & Project ManagementAuto-check passed
  • Ralph Tui Create Beads

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed
  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Product & Project ManagementAuto-check passed
  • Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).

    2.5k GitHub starsUsed in 1 repo~2.8k tokens
    Product & Project ManagementAuto-check passed
  • To Spec

    bestofjs/bestofjs

    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    3.1k GitHub starsUsed in 21 repos~757 tokens
    Product & Project ManagementAuto-check passed
  • Ralph Tui Create JSON

    subsy/ralph-tui

    Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed

More from Owl-Listener/inclusive-design-skills

All 55 skills in this repo
  • Assistive Technology Scenarios

    Owl-Listener/inclusive-design-skills

    Writes usage scenarios, use cases and storyboards that show real people using screen readers, switches, voice control and other assistive technology to finish tasks.

    105 GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check passed
  • Error Prevention and Recovery

    Owl-Listener/inclusive-design-skills

    Designs forgiving forms and flows: prevent input errors, write messages that say what happened and what to do, and add undo, confirmation and recovery paths.

    105 GitHub stars~739 tokensUpdated 4 mo ago
    Auto-check passed
  • Accessible Heading Structure

    Owl-Listener/inclusive-design-skills

    Designs heading hierarchies for screen reader navigation and cognitive accessibility on pages, articles, dashboards and forms.

    105 GitHub stars~763 tokensUpdated 4 mo ago
    Auto-check passed
  • Ability Spectrum Mapping

    Owl-Listener/inclusive-design-skills

    Maps a feature across a range of vision, hearing, motor and cognitive ability to find where the design starts to fail, and to explain accessibility scope to stakeholders.

    105 GitHub stars~917 tokensUpdated 4 mo ago
    Auto-check passed
  • Accessibility Debt Tracking

    Owl-Listener/inclusive-design-skills

    Track and manage accessibility debt — known accessibility issues that have been deferred.

    105 GitHub stars~869 tokensUpdated 4 mo ago
    Auto-check passed
  • Accessibility Testing Strategy

    Owl-Listener/inclusive-design-skills

    Plan what to test, how to test, and who should test for accessibility.

    105 GitHub stars~1k tokensUpdated 4 mo ago
    Auto-check passed

Questions about Inclusive User Stories

What does Inclusive User Stories do?

Write user stories that account for disability and diverse abilities from the start. Inclusive User Stories is an agent skill from Owl-Listener/inclusive-design-skills. Write user stories that account for disability and diverse abilities from the start.

When should I use Inclusive User Stories?

Inclusive User Stories fits situations like: writing user stories; acceptance criteria; jobs to be done; as a user I want.

How do I install Inclusive User Stories in Claude Code?

Run `npx skills add Owl-Listener/inclusive-design-skills --skill inclusive-user-stories -a claude-code`. Or copy the skill folder (inclusive-personas/skills/inclusive-user-stories in Owl-Listener/inclusive-design-skills) into .claude/skills/inclusive-user-stories in your project. Claude Code loads it when a task matches its description.

How do I install Inclusive User Stories in Codex?

Run `npx skills add Owl-Listener/inclusive-design-skills --skill inclusive-user-stories -a codex`. Or copy the skill folder (inclusive-personas/skills/inclusive-user-stories in Owl-Listener/inclusive-design-skills) into .agents/skills/inclusive-user-stories in your project. Codex loads it when a task matches its description.

Can I use Inclusive User Stories in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/inclusive-design-skills --skill inclusive-user-stories -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/inclusive-user-stories, .gemini/skills/inclusive-user-stories, .github/skills/inclusive-user-stories and .opencode/skills/inclusive-user-stories in your project.

What does Inclusive User Stories need to run?

SKILL.md names no scripts, command-line tools or credentials: Inclusive User Stories is instructions for the agent only.

Does Inclusive User Stories access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Inclusive User Stories safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Inclusive User Stories use?

Inclusive User Stories is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Inclusive User Stories use?

About 919 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Inclusive User Stories?

Skills that share tags, products or a category with Inclusive User Stories: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Agile Product Owner (alirezarezvani/claude-skills, 28k stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Inclusive User Stories?

Owl-Listener (a GitHub user) maintains it in Owl-Listener/inclusive-design-skills, which has 105 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on June 9, 2026.

Source: Owl-Listener/inclusive-design-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.