Job stories skill

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria.

by phuryn·MIT license·★ 26,557 Stars on the repo·GitHub ↗

Use now

phuryn/main1 file shown

SKILL.md2.9 KB

Browse every file on GitHub↗

SKILL.md

Show the full text75 lines

job-stories/SKILL.md75 lines · 2.9 KB

PreviewCode

Outline

RawView on GitHub

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

1	---
2	name: job-stories
3	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."
4	---
5	# Job Stories
6
7	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.
8
9	Use when: Writing job stories, expressing user situations and motivations, creating JTBD-style backlog items, or focusing on user context rather than roles.
10
11	Arguments:
12	- `$PRODUCT`: The product or system name
13	- `$FEATURE`: The new feature to break into job stories
14	- `$DESIGN`: Link to design files (Figma, Miro, etc.)
15	- `$CONTEXT`: User situations or job scenarios
16
17	## Step-by-Step Process
18
19	1. Identify user situations that trigger the need
20	2. Define motivations underlying the user's behavior
21	3. Clarify outcomes the user wants to achieve
22	4. Apply JTBD framework: Focus on the job, not the role
23	5. Create acceptance criteria that validate the outcome is achieved
24	6. Use observable, measurable language
25	7. Link to design mockups or prototypes
26	8. Output job stories with detailed acceptance criteria
27
28	## Story Template
29
30	Title: [Job outcome or result]
31
32	Description: When [situation], I want to [motivation], so I can [outcome].
33
34	Design: [Link to design files]
35
36	Acceptance Criteria:
37	1. [Situation is properly recognized]
38	2. [System enables the desired motivation]
39	3. [Progress or feedback is visible]
40	4. [Outcome is achieved efficiently]
41	5. [Edge cases are handled gracefully]
42	6. [Integration and notifications work]
43
44	## Example Job Story
45
46	Title: Track Weekly Snack Spending
47
48	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).
49
50	Design: [Figma link]
51
52	Acceptance Criteria:
53	1. Display Spending Summary with 'Weekly Spending Overview' section
54	2. Real-Time Update when expense logged
55	3. Progress Indicator (progress bar showing 0-100% of weekly budget)
56	4. Remaining Budget Highlight in prominent color
57	5. Detailed Spending Log with breakdown by category
58	6. Notifications at 80% budget threshold
59	7. Weekend-Specific Reminder at 90% by Thursday evening
60	8. Easy Access and Navigation to detailed breakdown
61
62	## Output Deliverables
63
64	- Complete set of job stories for the feature
65	- Each story follows the 'When...I want...so I can' format
66	- 6-8 acceptance criteria focused on outcomes
67	- Stories emphasize user situations and motivations
68	- Clear links to design and prototypes
69
70	---
71
72	### Further Reading
73
74	- [Jobs-to-be-Done Masterclass with Tony Ulwick and Sabeen Sattar](https://www.productcompass.pm/p/jobs-to-be-done-masterclass-with) (video course)
75