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