Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cm:cm-jtbdThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Understand the job, not the customer.**
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.
Maps user Jobs to be Done across functional, emotional, and social dimensions using Christensen's theory. Guides interview discovery, opportunity scoring, and YAML output.
Uncover customer jobs, pains, and gains using a structured JTBD framework. Use when clarifying unmet needs, repositioning a product, or improving discovery and messaging.
Share bugs, ideas, or general feedback.
Understand the job, not the customer. People don't buy products — they hire them to get a job done.
cm-brainstorm-idea for deep customer contextWhen [SITUATION], I want to [MOTIVATION], so I can [EXPECTED OUTCOME]
| Dimension | Definition | Example |
|---|---|---|
| Functional | The core task to accomplish | "Get from A to B quickly" |
| Social | How the person wants to be perceived | "Be seen as a reliable professional" |
| Emotional | How the person wants to feel | "Feel confident in my decision" |
For each major job discovered, complete the canvas:
JOB STATEMENT:
When [situation], I want to [motivation], so I can [outcome]
FUNCTIONAL DIMENSION: [core task]
SOCIAL DIMENSION: [perception goal]
EMOTIONAL DIMENSION: [feeling goal]
FORCES PUSHING TO HIRE:
(+) Push: [what makes them switch from current solution]
(+) Pull: [what attracts them to new solution]
FORCES RESISTING HIRE:
(-) Anxiety: [fears about new solution]
(-) Habit: [attachment to old solution]
COMPETING SOLUTIONS CURRENTLY HIRED:
1. [direct competitor or workaround]
2. [indirect solution]
3. [do-nothing option]
OUTCOME METRICS (how customer measures success):
- Speed: [e.g., "get answer in <5 minutes"]
- Accuracy: [e.g., "zero errors in the output"]
- Effort: [e.g., "no manual steps required"]
Rate each outcome metric:
Scores ≥ 15 = underserved outcomes → highest priority to address.
Save JTBD canvas to docs/jtbd/jtbd-canvas-[date].md.
| Skill | Relationship |
|---|---|
cm-brainstorm-idea | UPSTREAM: JTBD feeds into strategic analysis |
cm-planning | DOWNSTREAM: Validated jobs inform feature plans |
cm-cro-methodology | COMPLEMENT: JTBD objections → CRO objection handling |
cm-dockit | OUTPUT: JTBD canvases are a document type in DocKit |