Paul Wilshaw · Designed for Humans

Free Claude skill

Free Claude skill: write better UX user stories

User Stories for UX is a free Claude skill that writes user stories in the Jobs To Be Done format and fills in the rest of the ticket for you. You get the problem statement, a testable hypothesis, metrics, scope and competitor examples, ready for Azure DevOps, Jira, Trello, Notion, Linear or GitHub Issues.

Download the skill (zip, 9 KB)

Why I made it

I've read a lot of user stories that start "As a user, I want a button". They tell you nothing about why anyone needs the button, so nobody can tell whether it worked.

Jobs To Be Done fixes that by starting with the situation people are in and the progress they're trying to make. The problem is that writing a proper story, with a hypothesis and metrics, takes time, so it gets skipped. This skill does the legwork and asks for the inputs a designer would need anyway.

What it writes

Every story uses this format:

When I'm reviewing a new release for stakeholders,
I want to see a plain-English summary of what changed,
So I can communicate updates to customers without reading code diffs.

It then fills in five sections:

  • Problem statement, written from the user's point of view, not the business's
  • Hypothesis, as "if we… then… because…", so the assumption behind the design is out in the open
  • Metrics, two to four of them, including at least one about what people actually do
  • Scope, listing what's in and what's out, linked to the Figma frames
  • Variations, three to six competitor or comparable examples, with what's useful about each

How it works

Before it writes anything, the skill asks for four things in one go: the Figma link, the ticket link (or confirmation that there isn't one yet), who it's assigned to, and any competitor references you've already collected. If you don't have references, it finds some itself, as long as web search is switched on in Claude.

It works out which tool you use from the ticket link, then puts each section where it belongs. In Jira the scope can go in acceptance criteria. In Trello it becomes a checklist you can tick off. In Notion it fills in your database properties as well as the page.

If there's no ticket yet and Claude is connected to your tool, it can create the story on your backlog and tell you where it is. If it isn't connected, it gives you the finished text, a suggested title and where to paste each part.

How to install it

  • In Claude, make sure code execution and file creation are switched on (Settings > Capabilities).
  • Go to Customize > Skills, click +, then Create skill, then Upload a skill.
  • Upload the zip file without unzipping it, and check the skill is switched on.

It works in Claude on the web, desktop and mobile. Skills in your Claude account also sync to Claude Code when you sign in with the same account. Anthropic's guide covers the details: Use skills in Claude.

Can I change it?

Yes, please do. It's licensed under Creative Commons Attribution 4.0, so you can adapt it for your team, or even your clients, as long as you credit Paul Wilshaw / Designed for Humans and link back to this page. Rename the sections in SKILL.md to match your own template, or edit the file for your tool in the references folder.

Want skills built around your team?

This is one of several Claude skills I use every day. The others handle automated design QA, Azure DevOps tickets and building accessible UI against a design system. You'll find them all on my Claude skills page. At Designed for Humans I write skills like these for design and product teams and train people to use them. If your skills need a design system to work from, Design Systems for Humans gives Claude your real tokens and components.

See how we can work together, or see all my AI projects.