Agent skill · writing content · borghei
job-stories
Jobs-to-Be-Done story writing that focuses on user situations and motivations rather than personas. Use to write When/Want/So backlog items, run a JTBD discovery canvas, apply INVEST, and convert user stories to job stories.
Why this skill is useful
Provides a structured approach to writing job stories that enhances clarity and focus on user outcomes, which the AI may not generate reliably on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Job Stories Expert Overview Write job stories using the Jobs-to-Be-Done (JTBD) framework. Unlike traditional user stories that focus on roles ("As a user..."), job stories focus on the situation, motivation, and desired outcome. This shift produces requirements that are more grounded in real user context and less likely to encode assumptions about who the user is. The format is When [situation], I want to [motivation], so I can [outcome]. Removing the role and describing the situation matters because the same person has different needs in different situations, different people in the same situation share needs, and situations are observable and testable while roles are abstract labels. Core Capabilities JTBD discovery canvas — surface functional/social/emotional jobs, pains, and gains, then map each to a job-story component. Story writing — author situations, motivations, and outcomes that are specific, solution-agnostic, and benefit-focused. Quality gating — apply the six INVEST criteria and write 6-8 outcome-focused acceptance criteria per story. Conversion & facilitation — convert traditional user stories to job stories and run story-writing workshops. When to Use Feature definition -- When you need to articulate what to build and why, grounded in user context. Backlog creation -- When populating a backlog with work items that stay focused on user outcomes. Requirement workshops -- When collaborating with stakeholders to define what "done" looks like. Design briefs -- When giving designers context about the situation and motivation behind a feature. When NOT to Use When you need strategic backlog items with business context -- use wwas/ instead. When you need lightweight stories for a team already fluent in user story format. When the work is purely technical with no direct user-facing situation. Clarify First Before writing job stories, confirm these inputs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/job-stories