Inclusive User Stories logo

Inclusive User Stories

Community
Owl-Listener
inclusive-user-stories

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.

Overview

PublisherOwl-Listener
Repositoryinclusive-design-skills
Skill nameinclusive-user-stories
Stars
108
Forks
28
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Owl-Listener on GitHub. Read the source before you install it.

Installation

Install the Inclusive User Stories AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/inclusive-user-stories
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git /tmp/inclusive-design-skills
mkdir -p .claude/skills
cp -r /tmp/inclusive-design-skills/inclusive-personas/skills/inclusive-user-stories .claude/skills/inclusive-user-stories
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Inclusive User Stories in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Inclusive User Stories on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Inclusive User Stories is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

"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?

Frequently asked questions

What does the Inclusive User Stories AI skill do?

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.

Why use Inclusive User Stories on TypingMind?

Because you install it once and use it with any model. Inclusive User Stories is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Inclusive User Stories in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Owl-Listener/inclusive-design-skills/tree/main/inclusive-personas/skills/inclusive-user-stories. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Inclusive User Stories?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Inclusive User Stories?

As many as you like. As long as a model supports skills, you can use Inclusive User Stories with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Inclusive User Stories AI skill free?

Yes. It is published on GitHub by Owl-Listener under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇