From pm-copilot
Use this skill when the user asks about "jobs to be done", "JTBD", "what job are users hiring us for", "demand-side thinking", "what progress are users trying to make", "why do users switch to our product", "what are users really trying to accomplish", "forces of progress", "push pull analysis", or wants to understand user motivation beyond surface-level feature requests. Also use this skill when analyzing customer churn or acquisition to understand the switching trigger.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-copilot:jtbd-analysisThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are applying demand-side JTBD analysis (Bob Moesta / Clay Christensen) to understand what progress users are trying to make, and why they hire or fire products. The goal is to find where users will change behavior — because context makes the irrational rational.
You are applying demand-side JTBD analysis (Bob Moesta / Clay Christensen) to understand what progress users are trying to make, and why they hire or fire products. The goal is to find where users will change behavior — because context makes the irrational rational.
Key principle: "People don't buy products; they hire them to make progress in their lives." — Clay Christensen
Read memory/user-profile.md for product context, and context/product/personas.md for user segments. Identify any existing JTBD insights already captured.
The JTBD framework starts not with the product, but with the moment a user decides something has to change.
Ask the user (or infer from the context):
This is the first thought moment — the triggering event. It could be: a painful event, a new constraint, a milestone, a social pressure, or a realization.
For the target user making a switch (from their current solution to ours), map the four forces:
Push forces — what's pushing them away from the status quo:
Pull forces — what's attracting them to the new solution:
Anxiety forces — what's making them hesitate to switch:
Habit forces — what's keeping them with the old way:
Write the job-to-be-done statement in this format:
Job statement: "When [situation / struggling moment], I want to [motivation / what progress they're trying to make], so I can [expected outcome — functional / emotional / social]."
Write three versions of the job statement:
The best positioning addresses all three. Most products only address the functional job — the emotional and social jobs are where differentiation lives.
Who or what is the user currently "hiring" to do this job?
This defines the true competitive set — which is often not who you think.
Produce a JTBD summary:
Struggling moment: [Triggering situation] Functional job: [What the user is trying to accomplish] Emotional job: [How they want to feel] Social job: [How they want to be seen] Current hire: [What they're using today and what's wrong with it] Switch trigger: [What specific event or threshold causes them to look for an alternative] Key push: [The biggest frustration with the status quo] Key pull: [The most attractive thing about the new solution] Key anxiety: [The biggest hesitation about switching] Key habit: [The most powerful inertia keeping them with the old way] Implications for us: [What this means for positioning, onboarding, and messaging]
Offer to add JTBD findings to memory/user-profile.md and to relevant persona sections.
npx claudepluginhub productfculty-aipm/pm-copilot-by-product-facultyAnalyzes customer contexts to uncover functional, emotional, and social Jobs to be Done (JTBD) for product positioning and messaging.
Analyzes customer research or product context to uncover functional, social, and emotional jobs to be done. Identifies pains, gains, prioritizes jobs, and suggests product implications.
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.