jobs-to-be-done

Identify customer jobs, pains, and gains using a structured JTBD framework.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Uncover customer jobs, pains, and gains in a structured JTBD format to inform discovery, messaging, and prioritization.

Core Features & Use Cases

  • Systematically map Functional, Social, and Emotional Jobs
  • Identify Pains (Challenges, Costliness, Common Mistakes, Unresolved Problems)
  • Define Gains (Expectations, Savings, Adoption Factors, Life Improvement)
  • Use cases include early discovery, positioning, and roadmap prioritization

Quick Start

Fill out the JTBD template with a target customer, documenting Functional, Social, and Emotional Jobs, then list Challenges, Costs, Mistakes, Unresolved Problems, and the expected Gains.

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 customer jobs, pains, and gains for product discovery?

To structure customer jobs, pains, and gains for product discovery, use a JTBD framework template that maps functional, social, and emotional jobs alongside challenges, costs, and expected gains to reveal true needs.

What is the jobs-to-be-done framework used for in market research?

The jobs-to-be-done framework in market research uncovers true customer needs by identifying functional, social, and emotional jobs, applying this analysis to early discovery, product messaging, and roadmap prioritization.

How do I document functional, social, and emotional jobs in a JTBD analysis?

To document functional, social, and emotional jobs in a JTBD analysis, fill out a structured template with a target customer, then list challenges, common mistakes, unresolved problems, and expected gains across all dimensions.

Can I use job analysis to prioritize my product roadmap?

Yes, you can use job analysis to prioritize your product roadmap by evaluating documented customer pains like costliness and common mistakes against expected gains, ensuring development targets true unresolved problems.

What do I need to start mapping customer pains and gains?

To start mapping customer pains and gains, you need a defined target customer and a YAML frontmatter with name and description in SKILL.md, which provides the template to document challenges, costs, and life improvements.