jobs-to-be-done
Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also trigger when investigating why users choose competitors, designing features around real customer needs, or reframing a value proposition. Covers JTBD interviews, competition analysis, and jobs-oriented roadmaps. For product positioning, see obviously-awesome. For rapid validation,
npx skills add wondelai/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 Framework Framework for discovering innovation based on a fundamental truth: customers don't buy products -- they "hire" them to do a specific job in their lives. ## Core Principle **Job to Be Done** = the progress a customer wants to make in specific circumstances. Key elements of the definition: - **Progress** (not goal, not solution) -- the customer wants to move from the current state to a better one - **Circumstances** -- context determines the job, not customer attributes (demographics are useless) - **Hiring/Firing** -- the customer actively chooses a product for the "job" ## Scoring **Goal: 10/10.** Score 1 point per satisfied row in the Quick Diagnostic (7 rows) plus up to 3 points for depth: +1 if all three job dimensions are evidenced, +1 if the job statement avoids any product/solution name, +1 if competition includes non-consumption. Bands: **9-10** = job stated without the product, all four forces mapped, three dimensions evidenced, non-obvious competition and Little Hire tracked; **5-6** = job named but one or two diagnostic rows fail (usually missing forces or emotional/social dimensions); **<=3** = product-first framing, demographic segmentation,
- Core Principle
- Scoring
- Three Dimensions of Every Job
- Framework
- 1. The Job Statement
- 2. Forces of Progress (Push, Pull, Anxiety, Habit)
- 3. The Big Hire & Little Hire
- 4. Competitive Landscape (Non-Obvious Competition)
- 5. Customer Discovery Interviews
- 6. Designing for the Job
- Common Mistakes
- Quick Diagnostic
- Further Reading
- About the Author
What does the jobs-to-be-done skill do?
Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also trigger when investigating why users choose competitors, designing features around real customer needs, or reframing a value proposition. Covers JTBD interviews, competition analysis, and jobs-oriented roadmaps. For product positioning, see obviously-awesome. For rapid validation,
How do I install it?
Run `npx skills add wondelai/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 wondelai/skills, a repository with 1,835 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.