Job Stories
- 1.9k installs
- 24.9k repo stars
- Updated July 3, 2026
- phuryn/pm-skills
job-stories writes JTBD backlog items with situation-motivation-outcome format and acceptance criteria.
About
The job-stories skill creates backlog items using When situation, I want motivation, so I can outcome format with detailed acceptance criteria focused on user context rather than roles. Process steps identify triggering situations, underlying motivations, desired outcomes, JTBD framing, observable measurable acceptance criteria, and design mockup links. Template includes title as job outcome, description sentence, design link, and six acceptance criteria covering situation recognition, motivation enablement, visible progress, efficient outcome achievement, edge cases, and integrations. Example covers weekly snack spending tracking scenario. Arguments accept product name, feature, design files, and user situation context. Use when writing job stories, JTBD backlog items, or expressing user situations instead of persona-role stories. When/I want/so I can job story sentence format. Acceptance criteria validate outcomes not role behaviors. JTBD focus on situation and motivation over personas.
- When/I want/so I can job story sentence format.
- Acceptance criteria validate outcomes not role behaviors.
- JTBD focus on situation and motivation over personas.
- Links to Figma or design files in each story.
- Six acceptance criteria per story template.
Job Stories by the numbers
- 1,899 all-time installs (skills.sh)
- +82 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #263 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
job-stories capabilities & compatibility
- Capabilities
- jtbd formatting · acceptance criteria · situation mapping · design linking
- Use cases
- planning · project management
What job-stories says it does
When [situation], I want to [motivation], so I can [outcome].
Focus on the job, not the role
npx skills add https://github.com/phuryn/pm-skills --skill job-storiesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.9k |
|---|---|
| repo stars | ★ 24.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 3, 2026 |
| Repository | phuryn/pm-skills ↗ |
How do I express user needs as situations rather than role-based user stories?
Write JTBD job stories with When/I want/so I can format and detailed outcome-focused acceptance criteria.
Who is it for?
Product teams using JTBD for backlog and discovery artifacts.
Skip if: Engineering task tickets without user outcome framing.
When should I use this skill?
User writes job stories, JTBD backlog items, or situation-based requirements.
What you get
Job stories with When/I want/so I can descriptions and measurable acceptance criteria.
- Job story backlog items
- Acceptance criteria lists
Files
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
1. Identify user situations that trigger the need 2. Define motivations underlying the user's behavior 3. Clarify outcomes the user wants to achieve 4. Apply JTBD framework: Focus on the job, not the role 5. Create acceptance criteria that validate the outcome is achieved 6. Use observable, measurable language 7. Link to design mockups or prototypes 8. 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: 1. [Situation is properly recognized] 2. [System enables the desired motivation] 3. [Progress or feedback is visible] 4. [Outcome is achieved efficiently] 5. [Edge cases are handled gracefully] 6. [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: 1. Display Spending Summary with 'Weekly Spending Overview' section 2. Real-Time Update when expense logged 3. Progress Indicator (progress bar showing 0-100% of weekly budget) 4. Remaining Budget Highlight in prominent color 5. Detailed Spending Log with breakdown by category 6. Notifications at 80% budget threshold 7. Weekend-Specific Reminder at 90% by Thursday evening 8. 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
---
Further Reading
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
What is the job story sentence format?
When [situation], I want to [motivation], so I can [outcome].
Do job stories use user roles?
No. Focus on situation and job context rather than persona roles.
How many acceptance criteria are typical?
Six criteria covering recognition, enablement, progress, outcome, edges, and integrations.
Is Job Stories safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.