How to use the Job Stories Writer agent skill

What the job-stories skill makes the agent do

The skill focuses on the situation a user is in and the outcome they want, rather than on who the user is. Each story follows the pattern 'When [situation], I want to [motivation], so I can [outcome]'. Under each story, the skill writes acceptance criteria that describe how you would tell the outcome was achieved.

The source defines a short process: identify the user situations that trigger the need, define the motivations behind the behaviour, clarify the outcomes, apply a Jobs-to-be-Done (JTBD) framing that focuses on the job rather than the role, then write observable, measurable acceptance criteria. If design files are supplied, the skill also links to them.

• Inputs it recognises: product name, feature, design link (for example Figma or Miro), and user situations or job scenarios.
• Output: a complete set of job stories for the feature, each with acceptance criteria.

Install the job-stories skill

Download the ZIP for this skill from this page. The skill is a folder containing a file named SKILL.md. You can install it in one of two ways.

For a personal install, unzip the file into ~/.claude/skills/. To limit it to one project, unzip it into the .claude/skills/ folder inside that project.

In the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.

• Personal: ~/.claude/skills/ (available across your projects).
• Project: .claude/skills/ inside the project folder (available only there).
• Claude apps: Settings → Capabilities → Skills, then upload the ZIP.

Trigger the skill with natural requests

You do not need a special command. The skill's description says to use it when you are writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations. Ask for those things in ordinary language and the agent should pick it up.

Give the agent the context it needs. The more concrete the situations you describe, the more specific the stories will be. The source lists four arguments you can name in your request: the product, the feature, the design link, and the user situations or scenarios.

• Write job stories for a new reminder feature in our budgeting app, using these situations: ...
• Turn this feature idea into JTBD-style backlog items with acceptance criteria.
• Express these user motivations as job stories, and link to the Figma file I'm sharing.

Read a worked example

The source includes one example. The title is 'Track Weekly Snack Spending'. The situation is preparing a weekly allowance for snacks, the motivation is seeing quickly how much has been spent so far, and the outcome is not running out of money before the weekend.

The acceptance criteria are concrete: a spending summary section, real-time updates when an expense is logged, a progress bar from 0 to 100% of the weekly budget, a notification at 80% of budget, and a reminder at 90% by Thursday evening. Use this as a model for how measurable the criteria should be.

Review and adjust the output

The skill shapes wording and structure from what you supply. It does not research your market or check facts about your users. Treat the stories as a draft for your team to test against real information.

The template includes six acceptance criteria covering recognising the situation, enabling the motivation, visible progress, efficient outcome, edge cases, and integrations and notifications. The output guidance asks for 6 to 8 criteria focused on outcomes. Check that each criterion can actually be observed or measured.

• Confirm each situation and motivation came from real user input, not invention.
• Make sure every criterion can be checked by someone on the team.
• Add the real design link where the story references one.