job-stories

Write Jobs-to-be-Done job stories with situation, motivation, and outcome.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/jason23452/my-skill --skill job-stories-jason23452
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: job-stories
Source: https://github.com/jason23452/my-skill/tree/main/flow/job-stories
Command: npx skills add https://github.com/jason23452/my-skill --skill job-stories-jason23452

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Role-based user stories often miss the context and trigger behind a requirement, producing shallow specifications. This Skill structures requirements as job stories that capture the situation, motivation, and desired outcome so teams understand why a feature matters. ## Core Features & Use Cases - Job Story Format: Enforces the "When [situation/trigger], I want to [motivation/action], so I can [observable outcome]" structure. - Acceptance Criteria Seeds: Generates Given/When/Then criteria covering permissions, empty states, invalid data, conflicts, and failures. - Use Case: During requirements gathering for a notification feature, write "When a payment fails, I want to receive an alert, so I can retry before the order is cancelled" instead of a generic user story. ## Quick Start Rewrite my role-based user stories for the checkout flow as job stories with acceptance criteria.

Frequently Asked Questions about job-stories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a job story for requirements?▼

Use the format: When [situation/trigger], I want to [motivation/action], so I can [observable outcome]. Focus on the entry situation and trigger rather than the user role, and state the desired visible outcome.

Job stories vs user stories: when should I use each?▼

Use job stories when the situation and trigger matter more than the actor, such as context-dependent requirements. Keep role-based user stories when the actor's identity genuinely drives the requirement.

How do I add acceptance criteria to a job story?▼

Write Given/When/Then seeds: Given the user is in the stated situation, When the trigger occurs, Then the system enables the outcome. Add edge cases for permissions, empty states, invalid data, conflicts, or failures.

When should I not use job stories?▼

Avoid replacing all user stories with job stories when the actor is more important than the situation. Also avoid writing implementation details as the motivation, and split stories with multiple unrelated triggers or outcomes.