Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nwave-ai/nw-jtbd-core
Core JTBD theory and job story format - job dimensions, job story template, job stories vs user stories, 8-step universal job map, outcome statements, and forces of progress
Passed 20 of 23 test cases with the skill, and 17 of 23 without it.
and 6 more in the full report
4 fixed16 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
Convert this requirement into a proper Job Story format: 'As a DevOps engineer, I want to receive Slack alerts when memory exceeds 90%, so that I can restart the service.' Follow standard job story structuring rules.
| Checked | Without skill | With skill |
|---|---|---|
| Uses the 'When [situation], I want to [motivation], so I can [outcome]' structure. | Passed | Passed |
| Omits persona references like DevOps engineer from the job story context. | Passed | Passed |
| Frames the motivation around desired capability rather than a specific solution like Slack alerts. | Missed | Passed |
The instructions your model reads when the skill loads.
Jobs-to-be-Done reframes product development around the progress customers seek rather than products they buy. Customers "hire" products to accomplish specific jobs. The job exists independently of any solution.
Every job has three dimensions. Capture all three during discovery -- functional jobs surface first, but emotional and social jobs drive switching decisions.
Functional: Practical task to accomplish. Measurable, concrete, articulated first.
Emotional: How the customer wants to feel (or avoid feeling). Internal, personal, often unarticulated.
Social: How the customer wants to be perceived. Identity, status, professional reputation.
| Dimension | Questions |
|---|---|
| Functional | "What were you trying to accomplish?" / "Walk me through what you did." |
| Emotional | "How did that make you feel?" / "What were you worried about?" |
| Social | "Who else was involved or affected?" / "What would others think?" |
Job stories emphasize situation and motivation rather than persona and action.
When [situation/context],
I want to [motivation/capability],
so I can [expected outcome/benefit].
test cases passed, vs 17 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.