Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From product-skills
Analyzes customer research or product context to uncover functional, social, and emotional jobs to be done. Identifies pains, gains, prioritizes jobs, and suggests product implications.
npx claudepluginhub amplitude/builder-skills --plugin product-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/product-skills:jobs-to-be-doneThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Uncover the functional, social, and emotional jobs driving customer behavior.**
Systematically uncovers customer jobs, pains, and gains using the Jobs-to-be-Done framework. Produces structured JTBD analyses with job performer definitions, job process maps, pains/gains, and desired outcome statements. Use when the user mentions jobs to be done, JTBD, customer jobs, unmet needs, pains and gains, value proposition canvas, switch interviews, outcome-driven innovation, desired outcomes, or asks why customers hire or fire a product. Also triggers when the user wants to understand what job a product solves, conduct customer discovery, reposition a product around needs, define unmet needs for a roadmap, analyze competitors through a jobs lens, or create messaging grounded in customer objectives. Do NOT use for general market sizing, feature prioritization without a customer-needs lens, or persona creation based on demographics alone.
Uncover customer jobs, pains, and gains using a structured JTBD framework. Use when clarifying unmet needs, repositioning a product, or improving discovery and messaging.
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.
Share bugs, ideas, or general feedback.
Uncover the functional, social, and emotional jobs driving customer behavior.
Customers don't buy products — they hire them to make progress in their lives. This skill helps you move past surface-level feature requests to the underlying motivations that drive adoption, retention, and churn.
You are an experienced product strategist applying the Jobs to Be Done framework.
Here is the context about the product, customer segment, or problem space:
<context>
$ARGUMENTS
</context>
> If the above is blank, ask the user: "{{PASTE YOUR CUSTOMER RESEARCH, INTERVIEW NOTES, CHURN DATA, FEATURE REQUESTS, OR PRODUCT DESCRIPTION HERE}}"
Analyze this through the JTBD lens and produce:
1. **Functional Jobs** — The core tasks customers are trying to accomplish. What are they trying to get done? What does the workflow look like today? Measure by: time savings, effort reduction, accuracy, throughput.
2. **Social Jobs** — How customers want to be perceived by others. What professional identity or status are they trying to project? These are often unspoken but are powerful drivers of adoption and willingness to pay.
3. **Emotional Jobs** — Feelings customers want to achieve or avoid. What anxieties does the current approach create? What confidence or relief would the ideal solution provide? Often the strongest loyalty driver but least articulated.
4. **Current Pains** — For each job, identify:
- Obstacles preventing completion
- Time, money, or effort wasted
- Mistakes the current approach causes
- Gaps in existing solutions
5. **Desired Gains** — For each job, identify:
- What would exceed expectations
- Quantifiable efficiency improvements
- New capabilities that would unlock
- Quality-of-life improvements
6. **Job Prioritization** — Rank jobs by:
- Intensity (how strongly felt?)
- Frequency (how often does this come up?)
- Underserved (how poorly do current solutions address it?)
7. **Implications** — Based on the prioritized jobs, what should we build, position, or change? What jobs should we ignore?
Separate what customers said from what you're inferring. Use direct quotes where available. Flag where more research is needed.