jobs-to-be-done

Q: How do I install jobs-to-be-done?

Run npx skills add https://github.com/pmprompt/claude-plugin-product-management --skill jobs-to-be-done in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/jobs-to-be-done/ (personal) or .claude/skills/jobs-to-be-done/ (project).

by pmprompt

Use when asked to "jobs to be done", "JTBD", "why customers churn", "prep for customer interviews", "hire and fire products", or "find real competitors". Helps discover unmet needs and the context behind purchasing decisions. The Jobs to be Done framework (created by Clayton Christensen and Bob Moesta) explains why customers hire and fire products.

Installs: 396
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/pmprompt/claude-plugin-product-management --skill jobs-to-be-done

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads jobs-to-be-done automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Domain Context

This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.

Input Requirements

Context about your product, feature, or problem
Relevant data, research, or constraints (recommended but optional)
Clear articulation of what you're trying to achieve

Jobs-to-be-Done (JTBD)

What It Is

Jobs-to-be-Done is a framework for understanding customer motivation. The core insight: people don't buy products, they hire them to make progress in their lives.

When someone buys a product, they're not buying features or benefits—they're hiring that product to do a job. Understanding that job unlocks everything: positioning, messaging, feature prioritization, and competitive strategy.

The key shift: Move from asking "What do customers want?" to asking "What progress are customers trying to make?"

When to Use It

Use JTBD when you need to:

Understand why customers buy (not just what they buy)
Discover your true competitive set (often not who you think)
Find product-market fit for a new product or feature
Improve positioning and messaging that resonates
Reduce churn by understanding why customers leave
Prioritize your roadmap based on real customer progress
Identify new market opportunities through struggling moments

When Not to Use It

There's no real customer choice (e.g., employer-mandated software)
The purchase is pure habit with no conscious decision
You want to validate a hypothesis you've already decided on

Resources

Books:

Demand-Side Sales by Bob Moesta
Competing Against Luck by Clayton Christensen
When Coffee and Kale Compete by Alan Klement

FAQ

What does the jobs-to-be-done skill do?

How do I install jobs-to-be-done?

Run npx skills add https://github.com/pmprompt/claude-plugin-product-management --skill jobs-to-be-done in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/jobs-to-be-done/ (personal) or .claude/skills/jobs-to-be-done/ (project).

Which AI agents can use jobs-to-be-done?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is jobs-to-be-done safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains jobs-to-be-done?

It is published by pmprompt in pmprompt/claude-plugin-product-management. It has 396 recorded installs.