Jobs To Be Done
- 349 installs
- 43 repo stars
- Updated March 7, 2026
- pmprompt/claude-plugin-product-management
jobs-to-be-done is a Claude Code product management skill that applies the JTBD framework to uncover why customers hire and fire products for developers who need outcome-driven positioning, churn analysis, and roadmap pr
About
jobs-to-be-done is a product management skill from pmprompt/claude-plugin-product-management that implements Clayton Christensen and Bob Moesta's Jobs to be Done framework inside Claude Code. Instead of demographic personas, the skill reframes discovery around the progress customers seek—functional, emotional, and social jobs—when they choose, switch, or abandon software. It activates on JTBD, churn analysis, customer interview prep, hire-and-fire product decisions, and true competitor identification. The workflow expects product context plus optional research data, then shifts questions from what customers want to what progress they are trying to make. Developers and PMs reach for jobs-to-be-done when positioning messaging feels feature-led, churn root causes are unclear, or roadmap bets need validation against real struggling moments rather than assumed user wants.
- Job story writing
- Outcome-driven scope
- Competing with non-consumption
- Interview synthesis
- MVP boundary setting
Jobs To Be Done by the numbers
- 349 all-time installs (skills.sh)
- +12 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #834 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/pmprompt/claude-plugin-product-management --skill jobs-to-be-doneAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 349 |
|---|---|
| repo stars | ★ 43 |
| Last updated | March 7, 2026 |
| Repository | pmprompt/claude-plugin-product-management ↗ |
How do you apply Jobs to be Done framework?
Uncover the functional, emotional, and social jobs customers hire a product to do, reframing features around outcomes instead of demographic personas.
Who is it for?
Product managers and engineers doing discovery who need outcome-based positioning, churn diagnosis, or interview prep grounded in JTBD rather than feature lists.
Skip if: Purchases with no customer choice, pure habit buys, or teams that already decided on a hypothesis and only want confirmation.
When should I use this skill?
A user mentions JTBD, jobs to be done, customer churn reasons, hire-and-fire products, or preparing customer discovery interviews.
What you get
JTBD job statements, struggling-moment maps, reframed positioning angles, and a prioritized list of outcome-driven roadmap bets.
- JTBD job map
- positioning reframe
- competitive set analysis
By the numbers
- References 3 canonical JTBD books including Competing Against Luck
Files
Domain Context
This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.
Input Requirements
- Context about your product, feature, or problem
- Relevant data, research, or constraints (recommended but optional)
- Clear articulation of what you're trying to achieve
Jobs-to-be-Done (JTBD)
What It Is
Jobs-to-be-Done is a framework for understanding customer motivation. The core insight: people don't buy products, they hire them to make progress in their lives.
When someone buys a product, they're not buying features or benefits—they're hiring that product to do a job. Understanding that job unlocks everything: positioning, messaging, feature prioritization, and competitive strategy.
The key shift: Move from asking "What do customers want?" to asking "What progress are customers trying to make?"
When to Use It
Use JTBD when you need to:
- Understand why customers buy (not just what they buy)
- Discover your true competitive set (often not who you think)
- Find product-market fit for a new product or feature
- Improve positioning and messaging that resonates
- Reduce churn by understanding why customers leave
- Prioritize your roadmap based on real customer progress
- Identify new market opportunities through struggling moments
When Not to Use It
- There's no real customer choice (e.g., employer-mandated software)
- The purchase is pure habit with no conscious decision
- You want to validate a hypothesis you've already decided on
Resources
Books:
- Demand-Side Sales by Bob Moesta
- Competing Against Luck by Clayton Christensen
- When Coffee and Kale Compete by Alan Klement
Further Reading
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kHow it compares
Pick jobs-to-be-done over generic PM templates when you need outcome-driven customer motivation analysis rather than persona-based feature brainstorming.
FAQ
What is the jobs-to-be-done skill?
jobs-to-be-done is a Claude Code skill that applies the JTBD framework created by Clayton Christensen and Bob Moesta. The skill helps teams understand why customers hire products to make progress, identify true competitors, and prioritize roadmaps around outcomes instead of demog
When should developers use jobs-to-be-done?
jobs-to-be-done fits early discovery when teams need to understand purchase motivation, reduce churn, improve positioning, find product-market fit, or prep customer interviews. The skill shifts questions from what users want to what progress they are trying to make.
What inputs does jobs-to-be-done need?
jobs-to-be-done works best with context about the product, feature, or problem plus optional research data and constraints. Clear articulation of the decision—positioning, churn, roadmap, or competitive strategy—helps the skill produce actionable JTBD outputs.