job-stories

Generate JTBD-style job stories with acceptance criteria from user situations and motivations.

Updated Apr 8, 2026

Search Tags:#backlog #product-management #acceptance-criteria #user-context #jtbd #job-stories

Ready to run

npx skills add https://github.com/martiraste-lgtm/claude-skills --skill job-stories-martiraste-lgtm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: job-stories
Source: https://github.com/martiraste-lgtm/claude-skills/tree/main/pm-execution-job-stories
Command: npx skills add https://github.com/martiraste-lgtm/claude-skills --skill job-stories-martiraste-lgtm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Job stories help teams express user situations and motivations in a clear, testable format, reducing ambiguity in backlog items and acceptance criteria.

Core Features & Use Cases

Generate JTBD-style job stories from user situations and motivations
Provide explicit acceptance criteria linked to outcomes for backlog items
Support quick templates to translate context into actionable tasks

Quick Start

Provide a complete job story example following the When [situation], I want to [motivation], so I can [outcome] format.

Frequently Asked Questions about job-stories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is a job story in product management and when should I use it?▼

A job story expresses user situations and motivations in a clear, testable format. Product teams use job stories to reduce ambiguity in backlog items and define explicit acceptance criteria linked to user outcomes.

How do I write job stories using the When I want so I can format?▼

To write job stories, structure your user context using the When [situation], I want to [motivation], so I can [outcome] template. This translates user motivations into actionable backlog items with structured acceptance criteria.

How do I generate acceptance criteria from user motivations for my product backlog?▼

Generate acceptance criteria from user motivations by applying the job stories template. Linking specific user situations and desired outcomes directly provides explicit, testable acceptance criteria for backlog items.

What is the best way to translate user context into actionable backlog items?▼

The best way to translate user context into actionable backlog items is generating JTBD-style job stories. This clarifies user situations and motivations, reducing ambiguity and providing quick templates for actionable tasks.

Can I use job stories to replace traditional user stories for defining acceptance criteria?▼

Yes, job stories replace traditional user stories by focusing on user situations and motivations rather than personas. This approach reduces ambiguity and provides explicit acceptance criteria directly linked to desired outcomes.

Why do my backlog items have ambiguous acceptance criteria and how can job stories help?▼

Backlog items lack clear acceptance criteria when user context is poorly defined. Job stories help by applying the When... I want... so I can... template to express motivations in a clear, testable format.