job-stories

Job Stories is a product-management skill that generates backlog items in the Jobs-to-be-Done format 'When [situation], I want to [motivation], so I can [outcome],' paired with detailed acceptance criteria. It solves the problem of user stories that anchor on roles and personas rather than the actual situation and motivation driving a user's behavior, shifting the focus to user context and desired outcomes so requirements describe the job to be done rather than who is doing it.

The skill accepts arguments for the product name, the feature to break down, a link to design files (Figma, Miro, etc.), and the user context or scenarios. It follows an eight-step process: identifying triggering situations, defining motivations, clarifying outcomes, applying the JTBD framing, writing outcome-validating acceptance criteria in observable and measurable language, linking to design mockups, and outputting the finished stories. It supplies a reusable story template and a worked example (tracking weekly snack spending) with six to eight acceptance criteria covering summaries, real-time updates, progress indicators, notifications, edge cases, and navigation. The documented deliverable is a complete set of job stories for a feature, each following the format with outcome-focused acceptance criteria and links to design.

It is intended for product managers, product owners, and teams writing JTBD-style backlog items, expressing user situations and motivations, or focusing on user context instead of roles. It is a single-file SKILL.md that produces written artifacts and includes a link to a Jobs-to-be-Done masterclass for further reading.