Does this skill require primary user interviews to function?

No, it is specifically designed for 'tiny teams' and uses AI-augmented synthesis from secondary research sources, though it can process existing transcripts if available.

What specific JTBD frameworks are supported?

The skill supports the Moesta/Spiek Four Forces framework for switch analysis and Tony Ulwick’s Outcome-Driven Innovation (ODI) for job mapping and outcome identification.

Can it analyze competitive products?

Yes, it uses WebSearch and WebFetch tools to conduct competitive job analysis, mapping how other products in the domain satisfy specific user jobs.

How is this skill triggered within Claude Code?

It is typically invoked via the /user-experience parent skill when the orchestrator detects keywords like 'JTBD', 'user motivation', or 'switch triggers'.

What is the confidence level of the generated job statements?

Outputs are classified as MEDIUM confidence because they are synthesized from AI patterns and secondary data; they serve as high-quality hypotheses to be validated.

UX Jobs-to-Be-Done (JTBD) Researcher

Name: UX Jobs-to-Be-Done (JTBD) Researcher
Author: geekatron

bygeekatron

•

디자인 도구

Conducts Jobs-to-Be-Done research and analysis to uncover user motivations and innovation opportunities using proven frameworks.

The ux-jtbd sub-skill empowers small teams to perform deep user motivation analysis without extensive primary research resources. It leverages AI-augmented synthesis to create structured job statements, analyze switch forces (push, pull, anxiety, habit), and identify underserved outcomes using Outcome-Driven Innovation (ODI) methodologies. By shifting focus from feature-building to understanding what 'jobs' users hire products for, this skill helps teams define strategic product roadmaps and identify high-impact competitive differentiation opportunities.

주요 기능

01Outcome-Driven Innovation (ODI) for identifying underserved and overserved market outcomes

02Structured Job Statement Synthesis using the canonical Situation-Motivation-Outcome format

0316 GitHub stars

04Competitive Job Analysis to map how rival products address core user motivations

05Switch Interview Analysis applying Moesta/Spiek four forces framework (push, pull, anxiety, habit)

06Sequential Job Mapping to decompose complex user workflows into outcome-based steps

사용 사례

01Understanding the triggers that cause users to switch from a competitor to your solution

02Defining strategic product direction and problem-solving before entering the design phase

03Identifying high-value innovation opportunities for small teams with limited research budgets

주요 기능

01Outcome-Driven Innovation (ODI) for identifying underserved and overserved market outcomes

02Structured Job Statement Synthesis using the canonical Situation-Motivation-Outcome format

0316 GitHub stars

04Competitive Job Analysis to map how rival products address core user motivations

05Switch Interview Analysis applying Moesta/Spiek four forces framework (push, pull, anxiety, habit)

06Sequential Job Mapping to decompose complex user workflows into outcome-based steps

사용 사례

01Understanding the triggers that cause users to switch from a competitor to your solution

02Defining strategic product direction and problem-solving before entering the design phase

03Identifying high-value innovation opportunities for small teams with limited research budgets