job-stories

Generate job stories with acceptance criteria using the Jobs-to-be-Done format.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/bowiemax/pm-skills --skill job-stories-bowiemax
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: job-stories
Source: https://github.com/bowiemax/pm-skills/tree/main/pm-execution/skills/job-stories
Command: npx skills add https://github.com/bowiemax/pm-skills --skill job-stories-bowiemax

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users articulate user needs and motivations in a structured format, moving beyond traditional user stories to focus on the underlying "job" a user is trying to get done.

Core Features & Use Cases

  • JTBD Framework: Generates job stories using the "When [situation], I want to [motivation], so I can [outcome]" format.
  • Acceptance Criteria: Creates detailed, outcome-focused acceptance criteria for each job story.
  • Use Case: A product manager needs to define user needs for a new budgeting feature. They can use this skill to generate job stories that capture the user's context, their desired progress, and the ultimate outcome they seek, ensuring the feature truly solves their problem.

Quick Start

Generate job stories for a new expense tracking feature for a personal finance app.

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 the Jobs-to-be-Done framework?

A job story captures user needs using the format 'When [situation], I want to [motivation], so I can [outcome]', focusing on the underlying job a user is trying to get done rather than their persona.

How do I write acceptance criteria for job stories?

Generate detailed, outcome-focused acceptance criteria for each job story by defining the specific conditions that must be met to ensure the user's motivation achieves the desired outcome in their given situation.

When should I use job stories instead of traditional user stories for product development?

Use job stories when you need to articulate user needs and motivations in a structured format, moving beyond traditional user stories to focus on user context, desired progress, and ultimate outcomes.

How do I create job stories for user research and backlog item creation?

Generate job stories by understanding user context, motivations, and desired outcomes, then format them as 'When [situation], I want to [motivation], so I can [outcome]' to create actionable backlog items.

Can I define user needs for a new feature using the JTBD framework?

Yes, you can generate job stories that capture the user's context, desired progress, and ultimate outcome to ensure a new feature truly solves the user's problem within the Jobs-to-be-Done framework.

What are the limitations of using job stories for backlog items?

Generating effective job stories requires a deep understanding of user context, motivations, and desired outcomes; without this foundational user research, the resulting stories and acceptance criteria may not accurately reflect actionable user needs.