job-stories has an agent break a feature into backlog items that start from a user situation. Each story states the situation, the motivation and the outcome, then lists observable acceptance criteria and links to the design. It takes the product, feature, design link and context as inputs.
What You Get
- A complete set of job stories for the feature
- A title, a description in the When, I want to, so I can format and a design link for each story
- Six to eight acceptance criteria per story focused on outcomes
- An example story with its criteria to calibrate the format
Common Use Cases
- Splitting a new feature into JTBD-style backlog items
- Rewriting role-based user stories around situations
- Adding acceptance criteria that test whether the outcome was achieved
What Makes It Unique
It writes from the situation and the job, with no persona or role. Acceptance criteria cover recognizing the situation, enabling the motivation, visible progress, edge cases and notifications.
Under The Hood
The skill is one SKILL.md of instructions with no bundled scripts and no commands. The agent works from the product, feature, design link and context you give it and writes the stories in the chat. It reaches no outside service.