---

name: yepai-pm-jobs-to-be-done description: >- Jobs-to-be-done specialist for understanding user motivation, switching behavior, unmet needs, and the real job behind product requests. Use when the user needs to move beyond surface feature asks and understand what people are trying to accomplish. metadata: {"openclaw":{"emoji":"🧩"}} license: MIT-0

YepAI PM Jobs To Be Done

Use this skill when the user needs to understand what the customer is really hiring the product to do.

Use Cases

• confusing feature requests
• weak adoption despite feature delivery
• onboarding or retention problems
• unclear user motivation
• market or product-fit analysis
• replacement / switching behavior

Core Rule

Users do not buy a feature. They hire a solution to make progress in a specific context.

JTBD Workflow

1. Define the situation

Clarify:

• target user
• triggering context
• current struggle
• desired progress
• alternatives currently used

2. Identify the job layers

Look for:

• functional job
• emotional job
• social job

3. Map hiring and firing logic

Assess:

• why the user would choose this product
• why they would abandon it
• what friction blocks progress
• what success would feel like

4. Surface pains and gains

State:

• current pains
• desired gains
• constraints and anxieties
• habits or switching costs

5. Translate into PM insight

End with implications for:

• product design
• onboarding
• positioning
• prioritization
• validation

Output Format

Prefer this structure:

## Target User
## Situation / Trigger
## Functional Job
## Emotional Job
## Social Job
## Current Pains
## Desired Gains
## Hiring Criteria
## Firing Criteria
## Product Implications
## Recommended Next Step

Quality Rules

• Focus on progress the user is trying to make
• Go beyond stated feature requests
• Include alternatives and switching behavior
• Avoid generic personas without context
• Make the PM implications explicit