job-stories

phuryn/pm-skills

Create job stories in 'When/I want/so I can' format with detailed acceptance criteria focused on user situations and outcomes.

Source View on skills.sh

What is job-stories?

This skill generates job stories using the Jobs-to-be-Done (JTBD) framework, emphasizing user situations and motivations rather than roles. Use it when writing backlog items, expressing user context, or creating outcome-focused acceptance criteria.

Generates job stories in 'When [situation], I want to [motivation], so I can [outcome]' format
Creates 6-8 detailed acceptance criteria per story focused on observable, measurable outcomes
Applies JTBD framework to shift focus from roles to jobs and user contexts
Links stories to design files (Figma, Miro, etc.) for visual reference
Produces complete story sets with situation recognition, motivation enablement, and outcome validation
Includes edge case handling and integration considerations in acceptance criteria

How to install job-stories

npx skills add https://github.com/phuryn/pm-skills --skill job-stories

Claude Code

Cursor

Windsurf

Cline

How to use job-stories

1.Provide the product/system name ($PRODUCT)
2.Specify the feature to break into job stories ($FEATURE)
3.Link design files from Figma, Miro, or similar ($DESIGN)
4.Describe user situations or job scenarios ($CONTEXT)
5.Review generated job stories in the 'When...I want...so I can' format
6.Validate acceptance criteria are observable and measurable
7.Link each story to corresponding design mockups
8.Use stories as backlog items or requirements documentation

Use cases

Good for

Writing JTBD-style backlog items for product features
Expressing user situations and underlying motivations in story format
Creating acceptance criteria that validate outcomes rather than features
Breaking down new features into job-focused stories with design mockups
Designing notification and feedback mechanisms tied to user outcomes

Who it's for

Product managers using Jobs-to-be-Done methodology
UX designers translating user research into actionable stories
Agile teams shifting from role-based to outcome-focused requirements
Product teams emphasizing user context and situations over personas

job-stories FAQ

What's the difference between job stories and user stories?

Job stories focus on user situations and motivations (the 'job' to be done) rather than roles. They use 'When [situation], I want [motivation], so I can [outcome]' instead of 'As a [role], I want [feature], so that [benefit]', emphasizing context over personas.

How many acceptance criteria should each job story have?

The skill generates 6-8 acceptance criteria per story, focusing on situation recognition, motivation enablement, progress visibility, outcome achievement, edge case handling, and integration/notifications.

Can I use this for existing features or only new ones?

While designed for new features, the skill can be applied to existing features to reframe them using the JTBD framework and improve acceptance criteria clarity.

Do I need design files to use this skill?

Design files are optional but recommended. You can provide a link to Figma, Miro, or other design tools, but the skill will generate stories even without them.

How does this help with product prioritization?

By focusing on user situations and outcomes rather than features, job stories clarify the actual value being delivered, making it easier to prioritize based on user needs and job importance.

Full instructions (SKILL.md)

Source of truth, from phuryn/pm-skills.

name: job-stories description: "Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations."

Job Stories

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format. Generates stories with detailed acceptance criteria focused on user situations and outcomes.

Use when: Writing job stories, expressing user situations and motivations, creating JTBD-style backlog items, or focusing on user context rather than roles.

Arguments:

$PRODUCT: The product or system name
$FEATURE: The new feature to break into job stories
$DESIGN: Link to design files (Figma, Miro, etc.)
$CONTEXT: User situations or job scenarios

Step-by-Step Process

Identify user situations that trigger the need
Define motivations underlying the user's behavior
Clarify outcomes the user wants to achieve
Apply JTBD framework: Focus on the job, not the role
Create acceptance criteria that validate the outcome is achieved
Use observable, measurable language
Link to design mockups or prototypes
Output job stories with detailed acceptance criteria

Story Template

Title: [Job outcome or result]

Description: When [situation], I want to [motivation], so I can [outcome].

Design: [Link to design files]

Acceptance Criteria:

[Situation is properly recognized]
[System enables the desired motivation]
[Progress or feedback is visible]
[Outcome is achieved efficiently]
[Edge cases are handled gracefully]
[Integration and notifications work]

Example Job Story

Title: Track Weekly Snack Spending

Description: When I'm preparing my weekly allowance for snacks (situation), I want to quickly see how much I've spent so far (motivation), so I can make sure I don't run out of money before the weekend (outcome).

Design: [Figma link]

Acceptance Criteria: