Jobs To Be Done

This prompts Claude to map user motivations using the Jobs-to-Be-Done framework instead of jumping straight to features. It breaks down why people "hire" your product across functional, emotional, and social dimensions, then structures it into job statements like "When [situation], I want to [motivation], so I can [outcome]." The real value is in the full job lifecycle mapping, from define through conclude, which helps you spot where current solutions fall short. Use this when you're deciding what to build next or trying to understand why users behave a certain way. It's particularly good at reframing product decisions away from competitor feature checklists and toward actual user problems worth solving.

skills.sh installs: 2.3K
GitHub stars: 3.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add owl-listener/designer-skills --skill jobs-to-be-done --agent claude-code

Installs into .claude/skills of the current project.

Files

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].