Use when asked to "jobs to be done", "JTBD", "why customers churn", "prep for customer interviews", "hire and fire products", or "find real competitors".
Use when asked to "jobs to be done", "JTBD", "why customers churn", "prep for customer interviews", "hire and fire products", or "find real competitors".
Helps discover unmet needs and the context behind purchasing decisions.
The Jobs to be Done framework (created by Clayton Christensen and Bob Moesta) explains why customers hire and fire products.
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars49
LicenseLICENSE
Default branchmain
Open issues2
Status
Active
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md2,286 B
docsSUMMARY.md2,246 B
History
First seen on skills.sh
First recorded snapshot · 374 installs
SKILL.md
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