audit-stories
starsforks
How to install audit-stories?
owl-listener/inclusive-design-skills/audit-stories
$npx -y skills add Owl-Listener/inclusive-design-skills --skill audit-storiesAudit user stories for disability inclusion. Chains: inclusive-user-stories, edge-case-identification. Use when reviewing an existing backlog, sprint, or set of user stories to check whether they account for diverse abilities.
SKILL.md
| 1 | # Audit User Stories for Inclusion |
| 2 | |
| 3 | Review an existing set of user stories and identify where disability |
| 4 | and diverse abilities have been overlooked — then add the missing |
| 5 | criteria without creating separate accessibility tickets. |
| 6 | |
| 7 | ## Process |
| 8 | |
| 9 | ### Step 1: Gather Stories |
| 10 | Collect the user stories to audit. This could be a sprint backlog, |
| 11 | a feature's full story set, or an epic. |
| 12 | |
| 13 | ### Step 2: Check Each Story |
| 14 | Using **inclusive-user-stories**, review each story's acceptance |
| 15 | criteria for: |
| 16 | - Keyboard operability |
| 17 | - Screen reader support |
| 18 | - Visual accessibility (contrast, colour independence, zoom) |
| 19 | - Motor accessibility (target size, timing, precision) |
| 20 | - Cognitive accessibility (plain language, error recovery, undo) |
| 21 | |
| 22 | Flag any story where one or more of these are missing. |
| 23 | |
| 24 | ### Step 3: Check for Assumption Bias |
| 25 | Using **edge-case-identification**, for each story ask: |
| 26 | - What input method does this assume? |
| 27 | - What sensory ability does this assume? |
| 28 | - What cognitive capacity does this assume? |
| 29 | - What context does this assume? |
| 30 | - What "edge cases" have been dismissed that are daily reality |
| 31 | for some users? |
| 32 | |
| 33 | ### Step 4: Add Missing Criteria |
| 34 | For each flagged story, write the specific acceptance criteria that |
| 35 | need to be added. Don't create separate stories — add directly to |
| 36 | the existing ones. |
| 37 | |
| 38 | ## Output |
| 39 | |
| 40 | Deliver an audit report: |
| 41 | |
| 42 | 1. **Summary** — number of stories reviewed, number with gaps, |
| 43 | most common gap type |
| 44 | 2. **Story-by-story findings** — each story with its missing |
| 45 | criteria listed |
| 46 | 3. **Added criteria** — the specific acceptance criteria to add |
| 47 | to each story, ready to paste into the backlog |
| 48 | 4. **Patterns** — recurring gaps that suggest a systemic issue |
| 49 | (e.g., "no story in this sprint mentions keyboard access") |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
