jtbd-extractor

Extract Jobs-to-be-Done statements from interview transcripts and customer research data.

Updated May 18, 2026
One-click install
npx skills add https://github.com/fahadnari/Claude-skills --skill jtbd-extractor-fahadnari
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jtbd-extractor
Source: https://github.com/fahadnari/Claude-skills/tree/main/jtbd-extractor/jtbd-extractor
Command: npx skills add https://github.com/fahadnari/Claude-skills --skill jtbd-extractor-fahadnari

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw customer research is full of feature requests and scattered feedback that obscure what users are actually trying to accomplish. This Skill converts interview transcripts, survey responses, and support tickets into structured Jobs-to-be-Done statements so you can prioritize real user needs over surface-level requests. ## Core Features & Use Cases - JTBD Statement Extraction: Formats each job as "When [situation], I want to [action], so I can [outcome]" and categorizes jobs as Functional, Emotional, or Social. - Opportunity Scoring: Ranks jobs using Importance + (Importance - Satisfaction) to surface underserved needs, with confidence caveats when scores are inferred. - Feature Request Translation: Maps what users asked for (e.g., "add a dashboard") to the underlying job (e.g., "know if I'm on track without manual checking"). - Use Case: Paste a batch of customer interview transcripts and receive a ranked table of jobs with supporting quotes, a comparison against your existing personas.md, and top opportunities worth solving. ## Quick Start Ask the assistant to extract Jobs-to-be-Done statements from your pasted interview transcripts and rank them by opportunity score.

Frequently Asked Questions about jtbd-extractor

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

FAQPage Schema
How do I extract Jobs-to-be-Done from customer interviews?▼

Provide interview transcripts or notes, and the Skill identifies statements revealing what users are trying to accomplish, then formats each as "When [situation], I want to [action], so I can [outcome]." It looks beyond literal requests to the underlying goal.

What is the JTBD opportunity score formula?▼

Opportunity equals Importance plus (Importance minus Satisfaction), based on the Christensen/Ulwick framework. Higher scores indicate underserved jobs worth prioritizing, though scores inferred from limited qualitative data should be validated with quantitative research.

What research data do I need for JTBD analysis?▼

You need interview transcripts or notes, open-ended survey responses, support tickets, feature requests, or customer feedback. The Skill will not generate placeholder output without actual research data, and it can read files from your context folder.

Can JTBD analysis connect to my existing user personas?▼

Yes. If you maintain a personas.md context file, the analysis compares newly extracted jobs against existing persona JTBD statements and reports which jobs confirm, expand, or contradict your current understanding.

What are the limitations of qualitative JTBD scoring?▼

Importance and satisfaction scores estimated from a small set of interviews are directional only. The Skill flags low-confidence scores and recommends validating them with quantitative surveys before making prioritization decisions.