jobs-to-be-done

Structure customer interview findings into functional, social, and emotional job statements.

1|1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/yuyuxinli/moodcoco --skill jobs-to-be-done-yuyuxinli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jobs-to-be-done
Source: https://github.com/yuyuxinli/moodcoco/tree/main/.claude/skills/jobs-to-be-done
Command: npx skills add https://github.com/yuyuxinli/moodcoco --skill jobs-to-be-done-yuyuxinli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps product teams move beyond feature requests to a clear understanding of what customers are trying to accomplish (functional, social, emotional jobs), the obstacles they face, and the outcomes that would drive adoption.

Core Features & Use Cases

  • Structured JTBD Template: Step-by-step prompts and a fillable template to capture verb-driven, solution-agnostic jobs.
  • Pains and Gains Mapping: Guided sections for challenges, costliness, common mistakes, expectations, savings, and adoption factors to prioritize opportunities.
  • Practical Applications: Use during early discovery, product-market fit validation, roadmap prioritization, competitive analysis, and messaging refinement, with example analyses for reference.

Quick Start

Use the jobs-to-be-done template to map functional, social, and emotional jobs for a specific persona from a recent customer interview.

Frequently Asked Questions about jobs-to-be-done

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure user research findings into jobs-to-be-done statements?

To structure user research into jobs-to-be-done statements, capture verb-driven, solution-agnostic jobs categorized by functional, social, and emotional dimensions. This method transforms raw customer interview findings into clear statements of what customers are actually trying to accomplish.

What is the best way to map customer pains and gains for product-market fit validation?

Mapping customer pains and gains for product-market fit involves identifying obstacles, costliness, and common mistakes alongside expected savings and adoption factors. This structured mapping helps prioritize opportunities by ranking pain intensity and tying measurable gains to adoption factors.

How can I use the JTBD framework for early-stage product discovery?

Using the JTBD framework for early-stage product discovery requires applying a structured template to extract functional, social, and emotional jobs from target personas. This process moves teams beyond feature requests to understand the outcomes that would drive actual adoption.

When do I need to use jobs-to-be-done analysis instead of tracking feature requests?

You need jobs-to-be-done analysis when feature requests fail to reveal the underlying value proposition or user goals. It uncovers the functional, social, and emotional jobs customers are trying to accomplish, the obstacles faced, and outcomes driving adoption.

Does the jobs-to-be-done method work for competitive analysis and marketing messaging?

The jobs-to-be-done method works for competitive analysis and marketing messaging by producing solution-agnostic job statements and measurable gains. Refining messaging around these ranked pains and expected outcomes clarifies the value proposition.

How do I prioritize roadmap features based on customer interview data?

Prioritize roadmap features from customer interview data by ranking identified pains by intensity and aligning features with measurable gains tied to adoption factors. This ensures development targets the functional, social, and emotional jobs that matter most.