A job story uses the 'When [situation], I want to [motivation], so I can [outcome]' format to focus on user context and desired outcomes, not on user roles, typically for JTBD-style backlog items.

How many acceptance criteria should a story have?

Aim for 6-8 acceptance criteria that are observable and measurable, covering recognition, motivation enablement, progress feedback, outcome achievement, edge cases, and integrations.

How do I connect job stories to design artifacts?

Provide a Design link in each story and ensure the story references the relevant design mockups or prototypes (e.g., Figma, Miro) to validate the proposed outcomes.

job-stories

Scanned

npx machina-cli add skill phuryn/pm-skills/job-stories --openclaw

Files (1)

SKILL.md

2.9 KB

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:

Display Spending Summary with 'Weekly Spending Overview' section
Real-Time Update when expense logged
Progress Indicator (progress bar showing 0-100% of weekly budget)
Remaining Budget Highlight in prominent color
Detailed Spending Log with breakdown by category
Notifications at 80% budget threshold
Weekend-Specific Reminder at 90% by Thursday evening
Easy Access and Navigation to detailed breakdown

Output Deliverables

Complete set of job stories for the feature
Each story follows the 'When...I want...so I can' format
6-8 acceptance criteria focused on outcomes
Stories emphasize user situations and motivations
Clear links to design and prototypes

Source

git clone https://github.com/phuryn/pm-skills/blob/main/pm-execution/skills/job-stories/SKILL.mdView on GitHub

Overview

Generates job stories using the standard 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. It helps teams express user contexts and outcomes for JTBD-style backlog items and ensures alignment with design prototypes.

How This Skill Works

The tool prompts for key context fields ($PRODUCT, $FEATURE, $DESIGN, $CONTEXT), then guides you through identifying user situations, defining motivations, and clarifying outcomes. It applies a JTBD-focused approach, creates acceptance criteria, uses observable language, and links to design files to produce complete job stories ready for backlogs and milestones.

When to Use It

When drafting backlog items for a new feature using JTBD-style stories
When you want to emphasize user situations and motivations over user roles
When you need acceptance criteria that validate outcomes in observable terms
When aligning requirements with design prototypes or mockups
When producing a complete set of job stories for a feature sprint or roadmap

Quick Start

Step 1: Define $PRODUCT, $FEATURE, and $CONTEXT to scope the story
Step 2: Write the core sentence 'When [situation], I want to [motivation], so I can [outcome]' and draft 6-8 measurable acceptance criteria
Step 3: Link to Design files (Figma/Miro) and finalize the output as a complete job story

Best Practices

Start with real user situations that trigger the need
Tie motivations directly to concrete outcomes
Write acceptance criteria in observable, measurable terms
Link every story to design files or prototypes
Keep the focus on the job to be done, not the user role

Example Use Cases

Track Weekly Snack Spending
Onboard a New Employee Quickly
Validate Feature Usage with Real-Time Metrics
Plan Travel Within Budget Rules
Prepare Standup Focus Plan Aligned with Priorities

Frequently Asked Questions

Add this skill to your agents