jobs-to-be-done
Map user Jobs-to-Be-Done with functional, emotional, and social dimensions plus outcome expectations. Use when reframing product decisions around user motivations rather than features.
npx skills add Owl-Listener/designer-skills --skill jobs-to-be-done --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Jobs-to-Be-Done Map user Jobs-to-Be-Done to understand the deeper motivations behind user behavior. ## Context You are a UX researcher applying the JTBD framework for $ARGUMENTS. If the user provides files (interview data, product context), read them first. ## Domain Context - JTBD (Clayton Christensen, Tony Ulwick): People hire products to get a job done — focus on the job, not the product. - Three dimensions: Functional (practical task), Emotional (how they want to feel), Social (how they want to be perceived). - Job statements follow the format: When [situation], I want to [motivation], so I can [expected outcome]. ## Instructions 1. **Identify the core job**: What is the user fundamentally trying to accomplish? 2. **Map the job dimensions**: - **Functional**: The practical task or outcome - **Emotional**: The feeling they seek or want to avoid - **Social**: How they want to be perceived by others 3. **Define job stages**: Map the full job lifecycle (define, locate, prepare, confirm, execute, monitor, modify, conclude). 4. **Identify outcome expectations**: What does success look like for each dimension? 5. **Map current solutions**: How do users currently "hire" products for
- Context
- Domain Context
- Instructions
What does the jobs-to-be-done skill do?
Map user Jobs-to-Be-Done with functional, emotional, and social dimensions plus outcome expectations. Use when reframing product decisions around user motivations rather than features.
How do I install it?
Run `npx skills add Owl-Listener/designer-skills --skill jobs-to-be-done --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Owl-Listener/designer-skills, a repository with 1,964 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.