pm-personas-jtbd

Builds research-grounded user personas and Jobs-to-Be-Done framings for product decisions.

12|2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Uxcel-Lab/product-skills --skill pm-personas-jtbd-uxcel-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-personas-jtbd
Source: https://github.com/Uxcel-Lab/product-skills/tree/main/pm/foundations/personas-jtbd
Command: npx skills add https://github.com/Uxcel-Lab/product-skills --skill pm-personas-jtbd-uxcel-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams routinely get personas that are invented demographic fiction — plausible-sounding characters with no research basis, needs inferred from age and income, and lifestyle trivia that never changes a design decision. This Skill replaces that failure mode with a disciplined process for building audience-understanding artifacts grounded in real research. ## Core Features & Use Cases - Lens selection by objective: Decides between personas, Jobs-to-Be-Done, or both based on research objective, product stage, available data, and resources. - Research-grounded construction: Enforces psychographics-first detail, keeps only attributes that change a design decision, caps the set at roughly 3-5 personas with one primary, and labels proto-personas as untested assumptions. - Validation hand-off: Routes the finished artifact through an assumption-rigor audit to flag needs and behaviors that rest on assumption rather than evidence. - Use Case: A PM asks for personas for a new onboarding flow. The Skill first asks what research exists, recommends JTBD plus a proto-persona given only early interview data, drafts decision-relevant profiles, and flags which claims still need validation. ## Quick Start Ask the assistant to create user personas or a Jobs-to-Be-Done framing for your product, describing what research data you already have.

Frequently Asked Questions about pm-personas-jtbd

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

FAQPage Schema
How do I create user personas from real research?▼

Synthesize patterns from interviews, field studies, surveys, and analytics into a character where every detail could change a design decision. Lead with psychographics like goals and pain points, include demographics only when relevant to product use, and keep the set to roughly 3-5 personas.

Personas vs Jobs-to-Be-Done: which should I use?▼

Choose by research objective: JTBD for understanding motivations and unmet needs or early-stage innovation, personas for team alignment and marketing around who the user is. For guiding product development, use both — personas for the who, JTBD for the job.

Can AI generate user personas without research data?▼

AI-generated personas without real data reproduce generic internet stereotypes and underrepresent edge cases and minority users. Use AI only to cluster transcripts and draft profiles after collecting real data; without research, build a clearly labeled proto-persona and test it.

How many personas should a product have?▼

Most products need roughly 3-5 personas, up to 7 at most. Merge groups that would make the same design demands, drop segments too small to influence decisions, and designate one primary persona per product area whose needs take priority.

What details should a user persona include?▼

Include only attributes that would change a design decision, led by psychographics such as goals, motivations, pain points, and behaviors. Cut lifestyle trivia and demographic filler, and never infer needs from age, gender, or income alone.