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.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill jobs-to-be-donegit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/designer/design-research/skills/jobs-to-be-done ~/.claude/skills/jobs-to-be-donePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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. 2. **Map the job dimensions**:
3. - **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. 4. **Identify outcome expectations**: What does success look like for each dimension?
5. 5. **Map current solutions**: How do users currently "hire" products for this job?Details
- Skill name
jobs-to-be-done- Repository
- sethdford/claude-skills
- Path
designer/design-research/skills/jobs-to-be-done/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
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 the Jobs to Be Done skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Jobs to Be Done popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Lessons Learned
48sethdford/claude-skills
Conduct post-incident reviews to document lessons learned and implement process improvements preventing recurrence.
Interface Design
48sethdford/claude-skills
Designing minimal, cohesive, role-based interfaces that respect Interface Segregation Principle.
Log Aggregation
48sethdford/claude-skills
ELK Stack, structured logging, log query patterns, and centralized log management.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.