Individual skill

jtbd-extractor

Extracts Jobs To Be Done from qualitative research data - job stories in the "When I…, I want to…, so I can…" form, a forces-of-progress map (push, pull, anxiety, habit), and functional, emotional, and social dimensions, each backed by verbatim quotes. Use when someone says "extract the jobs from these interviews", "run a JTBD analysis on this diary study", "why do users switch to or from us", or has transcripts and wants solution-agnostic goals rather than feature requests. Do NOT use for clustering findings into themes across a study - use interview-synthesis instead; for building persona profiles from research, use user-persona; for planning the interviews themselves, use interview-guide-builder.

skills/jtbd-extractor/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 24
Repository last updated: Oct 13, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude Repository topic
claude-skills Repository topic
skill-me Repository topic
data Derived category
research Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 6,735 bytes

Read excerpt


# JTBD Extractor

Jobs To Be Done reframes research around the progress people are trying to make, not product features or user attributes - the Intercom/Ulwick lineage, not a cargo-culted template. The costly failure this skill prevents is shipping a "jobs inventory" that is really a feature wishlist with JTBD grammar pasted on: jobs contaminated with solution language are unstable, and a roadmap built on them chases tools instead of progress.

## Inputs to collect

1. The raw data: interview transcripts, diary-study entries, support tickets, or switch-moment notes. Verbatim material is required - summaries strip the quotes that serve as evidence. If only summaries exist, proceed but downgrade all evidence strength and say so.
2. Sample size and who was interviewed. Fewer than 5 participants means the inventory is directional; label it that way.
3. The decision the jobs will inform (roadmap, positioning, onboarding redesign). This sets granularity - positioning wants the main job; roadmap wants the sub-jobs.
4. Any existing jobs inventory to reconcile against, so new jobs merge rather than duplicate.

## Operating procedure

Order matters: forces are mapped per candidate job, so candidates must be isolated first; dimensions come last because they need the accumulated quote evidence.