Jobs To Be Done Analyzer

Uncover the real "job" customers hire your product to do. Goes beyond features to understand functional, emotional, and social motivations. Use when user says "jobs to be done", "jtbd", "why do customers", "what job", "customer motivation", "what problem", "user needs", "why do people buy".

Security Scan

The skill is an instruction-only Jobs-To-Be-Done analysis guide that asks for no credentials, installs nothing, and stays within its stated purpose.

Purpose & Capability

Name/description (JTBD analysis) match the actual content: SKILL.md plus references provide frameworks, templates and examples. No unrelated binaries, env vars, or platform access are requested.

Instruction Scope

Runtime instructions are limited to interviewing prompts, job-statement templates, and an output format. They do not direct the agent to read system files, access credentials, call external endpoints, or exfiltrate data.

Install Mechanism

No install spec and no code files — instruction-only skill. Nothing is written to disk or fetched at install time.

Credentials

The skill declares no required environment variables, config paths, or credentials. The content does not reference secrets or unrelated services.

Persistence & Privilege

always is false and default autonomous invocation is allowed (platform default). The skill does not request persistent or elevated system privileges.

Assessment

This skill is internally consistent and appears safe to add as a guidance/template tool. Before using it with real customer data, remove or anonymize personally identifiable information and sensitive business secrets in prompts. Note there is no homepage or author provenance listed—if provenance matters to you, ask the publisher for identity or audit trail. Finally, remember the skill can be invoked by your agent (normal for skills); if you prefer manual use only, disable autonomous invocation at the platform/agent level.

The Core Concept

Customers don't buy products. They HIRE products to do a job.

"People don't want a quarter-inch drill. They want a quarter-inch hole." Actually: They want a shelf → to display photos → to feel proud of family.

The Three Job Dimensions

Dimension	Question	Format
Functional	What task needs doing?	"Help me [verb] [object]"
Emotional	How do I want to feel?	"Make me feel [emotion]"
Social	How do I want to be seen?	"Help me be seen as [quality]"

The Process

1. Job Statement: "When [situation], I want to [motivation], so I can [outcome]"
2. Map all 3 dimensions for each user type
3. Find real competition: What ELSE could do this job?
4. Prioritize: Which jobs are most critical and underserved?

Output Format

PRODUCT: [What you're analyzing]

For [User Type]:
JOB: "When [situation], I want [motivation], so I can [outcome]"

📋 FUNCTIONAL: [Task to accomplish]
💜 EMOTIONAL: [Feeling desired]
👥 SOCIAL: [Perception desired]

ALTERNATIVES: [What else could do this job?]
UNDERSERVED: [What part isn't done well?]
PRIORITY: Critical / Important / Nice-to-have

Key Questions

1. "What were you trying to accomplish when you [action]?"
2. "Walk me through the last time you needed to [job]"
3. "What would you do if [product] didn't exist?"
4. "What's frustrating about how you currently [job]?"

Integration

Compounds with:

• first-principles-decomposer → Decompose job to atomic need
• cross-pollination-engine → Find how others solve similar jobs
• app-planning-skill → Use JTBD to inform features

---

See references/examples.md for Artem-specific JTBD analyses