jobs-to-be-done
Uncover customer jobs, pains, and gains in a structured JTBD format. Use when clarifying unmet needs, repositioning a product, or improving discovery and messaging.
npx skills add deanpeters/Product-Manager-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.
## Purpose Systematically explore what customers are trying to accomplish (functional, social, emotional jobs), the pains they experience, and the gains they seek. Use this framework to uncover unmet needs, validate product ideas, and ensure your solution addresses real motivations—not just surface-level feature requests. This is not a survey—it's a structured lens for understanding *why* customers "hire" your product and what would make them "fire" it. ## Input **Works best with:** The customer segment (or product whose customers) you're analyzing. **Also useful:** Interview notes, support tickets, or research to mine for jobs, pains, and gains; the situation or trigger you care about. Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line — counts as answers already given. Use it and skip whatever it covers; don't re-ask. **Arriving empty-handed? That works too.** The skill asks who the customer is and what progress they're trying to make before structuring the JTBD breakdown. **Example invocation:** `Run JTBD for freelance designers using our invoicing tool — here are 6 interview summaries.` ## Key Concep
- Purpose
- Input
- Key Concepts
- The Jobs-to-be-Done Framework
- Why This Structure Works
- Anti-Patterns (What This Is NOT)
- When to Use This
- When NOT to Use This
- Application
- Step 1: Define the Context
- Step 2: Explore Customer Jobs
- Step 3: Identify Pains
- Step 4: Uncover Gains
- Step 5: Prioritize and Validate
What does the jobs-to-be-done skill do?
Uncover customer jobs, pains, and gains in a structured JTBD format. Use when clarifying unmet needs, repositioning a product, or improving discovery and messaging.
How do I install it?
Run `npx skills add deanpeters/Product-Manager-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 deanpeters/Product-Manager-Skills, a repository with 6,255 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.