Jobs to be done
Skill Infrasity-Labs/dev-gtm-claude-skills/product-designers/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.From its SKILL.md
npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill jobs-to-be-doneAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.6 KB, 316 tokens by cl100k_base, as published. Nobody here has run it
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
- Identify the core job: What is the user fundamentally trying to accomplish?
- 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
- Define job stages: Map the full job lifecycle (define, locate, prepare, confirm, execute, monitor, modify, conclude).
- Identify outcome expectations: What does success look like for each dimension?
- Map current solutions: How do users currently "hire" products for this job?
- Find opportunities: Where are current solutions underserving the job?
- Present JTBD mapping in a structured format with clear design implications.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.