user-research · yonatangross — Claude Code skill: personas, journey maps, JTBD
Skill for structured user research: personas, journey maps, interviews, usability testing, and card sorting. Learn what users actually need and build products grounded in evidence.
MIT 134 installs ★ 305 updated 2026-11-07
npx skills add yonatangross/orchestkit --skill user-research -a claude-codeWhat user-research does
user-research provides templates and frameworks for core research methods. Personas are built from real data, capturing goals and pain points rather than demographics alone. Journey maps track the full lifecycle from awareness through retention, with touchpoints, actions, emotions, and opportunities at each stage. The JTBD framework reframes needs as jobs: when [situation], I want [motivation], so I can [outcome].
The skill includes tables for choosing methods by sample size and timeline, interview best practices (open questions, follow threads), journey structures for B2B SaaS cycles, and empathy maps for team workshops. Each method solves a specific problem: interviews for early discovery, surveys for validation, card sorting for information architecture.
Three rule sets provide depth: research-personas.md for persona maintenance, research-journey-mapping.md for service blueprints, research-user-interviews.md for scenarios and metrics (NPS, SUS). Ready-made interview templates and workshop guides are included. The skill uses Claude Code's native tools — no dependencies needed.
What it helps with
- build personas grounded in data instead of assumptions
- map the full user journey from first contact to retention
- run structured interviews and spot patterns in the data
- identify and articulate the actual job users are trying to do
- choose the right research method, sample size, and timeline
Example prompts for the agent
- Build a persona for a DevOps engineer: their goals, frustrations, and how they evaluate tools.
- Create a journey map for a B2B buyer: awareness, evaluation, purchase, onboarding, expansion.
- Write an interview guide to test whether self-service deployment is a real problem.
How to install user-research
1Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill user-research -a claude-code2Manually: put the files in place
~/.claude/skills/user-research/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/user-research/
1Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill user-research -a codex2Manually: put the files in place
.agents/skills/user-research/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill user-research -a cursor2Manually: put the files in place
.cursor/skills/user-research/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install yonatangross/orchestkit src/skills/user-research2Manually: put the files in place
.github/skills/user-research/SKILL.md1Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill user-research -a gemini-cli2Platform CLI
gemini skills install https://github.com/yonatangross/orchestkit --path src/skills/user-researchManually: put the files in place
.devin/skills/user-research/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add yonatangross/orchestkit --skill user-research -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about user-research
How do I install user-research in Claude Code?
Run npx skills add yonatangross/orchestkit --skill user-research -a claude-code, then open ~/.claude/skills/user-research/SKILL.md.
What does user-research do?
It supplies templates and guidance for user research: personas, journey maps, interview structure, JTBD analysis, empathy maps, and card sorting. It also covers research method selection, sample sizes, and how to synthesize findings into actionable insights.
How many people should I interview?
Start with 5–8 participants over 2–3 weeks for early discovery. This is enough to surface key patterns. Use surveys (100+) or A/B tests (1000+) once you have hypotheses to validate.
Source text
SKILL.md · MIT
--- name: user-research license: MIT compatibility: "Claude Code 2.1.277+." description: "Personas, journey maps, interview guides, usability tests, card sorting and Jobs-to-Be-Done. Use when planning user research." user-invocable: false disable-model-invocation: false metadata: owner-agent: "product-strategist" category: document-asset-creation version: "1.0.0" author: "OrchestKit" complexity: "medium" tags: "persona, journey-map, user-interview, usability, jtbd, card-sort, empathy-map, research" allowed-tools: "Read Glob Grep WebFetch WebSearch" --- # User Research Frameworks for building deep user understanding through structured research methods. Covers personas, journey mapping, interviews, usability testing, and Jobs-to-be-Done. ## Research Method Selection Choose the right method for your question: | Method | When to Use | Sample Size | Time | Output | |--------|-------------|-------------|------|--------| | User Interviews | Early discovery, deep understanding | 5-8 | 2-3 weeks | Qualitative insights | | Usability Testing | Validate designs, find issues | 5-10 | 1-2 weeks | Actionable fixes | | Surveys | Quantify attitudes, preferences | 100+ | 1-2 weeks | Statistical data | | Card Sorting | Information architecture | 15-30 | 1 week | IA recommendations | | A/B Testing | Compare alternatives | 1000+ | 2-4 weeks | Statistical winner | **Rule of thumb:** Start with interviews (5-8 participants) to discover unknowns. Switch to surveys once you have hypotheses to validate. ## Persona Quick Reference Personas are fictional composites built from research synthesis. Keep to 3-5 max. ```markdown ## Persona: [Name] ### Demographics - Age: [Range] - Role: [Job title] - Company: [Type/size] - Tech savviness: [Low/Medium/High] ### Quote > "[Characteristic statement that captures their mindset]" ### Goals 1. [Primary goal - what success looks like] 2. [Secondary goal] ### Pain Points 1. [Frustration with current state] 2. [Obstacle they face] ### Key Insight [The most important thing to remember about this persona] ``` **Incorrect — vague persona without goals:** ```markdown Persona: Sarah, Age 35, Marketing Manager. Likes social media and coffee. ``` **Correct — actionable persona with goals and pain points:** ```markdown Persona: DevOps Dana Quote: "I don't have time for tools that create more work than they save." Goals: Reduce deployment failures, give devs self-service capabilities Pain Points: Alert fatigue from false positives, context-switching between 10+ tools Key Insight: Evaluates tools by "time saved vs. time invested" — needs immediate value. ``` ## Journey Map Structure Maps the end-to-end experience for a specific persona and scenario. ```markdown ## Journey Map: [Journey Name] ### Persona + Scenario [Which persona | What they're trying to accomplish] ### Stages: Aware → Consider → Purchase → Onboard → Use → Retain For each stage: - **Touchpoints:** [Channel/interaction point] - **Actions:** [What user does] - **Emotions:** [Satisfied / Neutral / Frustrated] - **Pain Points:** [Friction] - **Opportunities:** [How we improve] ``` Common B2B SaaS stages: `Awareness → Evaluation → Purchase → Onboarding → Adoption → Expansion → Advocacy/Churn` ## JTBD Framework People don't buy products — they hire them to do specific jobs. **JTBD Statement Format:** ``` When [situation], I want to [motivation], so I can [expected outcome]. ``` **Example:** ``` When I'm preparing for a board review, I want to quickly see revenue trends, so I can answer questions confidently without scrambling for data. ``` **Job Dimensions:** | Dimension | Description | |-----------|-------------| | Functional | Practical task to accomplish | | Emotional | How the user wants to feel | | Social | How the user wants to be perceived | **Opportunity Score:** `Importance + (Importance - Satisfaction)` — scores > 10 indicate high-opportunity areas. ## Empathy Map Quick tool for building shared understanding in workshops: ``` +-------------------------+-------------------------------+ | SAYS | THINKS | | Direct quotes | Worries and concerns | | Questions asked | Aspirations | +-------------------------+-------------------------------+ | DOES | FEELS | | Observable actions | Emotional state | | Workarounds | Frustrations and delights | +-------------------------+-------------------------------+ | PAINS | GAINS | | Fears and obstacles | Wants and needs | +-------------------------+-------------------------------+ ``` ## Interview Best Practices | Do | Don't | |----|-------| | Ask open-ended questions | Ask leading questions | | Ask "why" and "how" | Accept surface answers | | Follow interesting threads | Stick rigidly to script | | Take verbatim notes | Paraphrase or interpret | **Standard interview arc:** Warm-up (5 min) → Context setting (10 min) → Deep dive (25 min) → Wrap-up (5 min) ## Rules (Load On-Demand) Read these files for detailed guidance: - [research-personas.md](rules/research-personas.md) — Persona template, empathy map, maintenance schedule - [research-journey-mapping.md](rules/research-journey-mapping.md) — Journey map template, service blueprints, experience curves - [research-user-interviews.md](rules/research-user-interviews.md) — Interview structure, usability testing, NPS/SUS, card sorting ## References - [interview-guide-template.md](references/interview-guide-template.md) — Ready-to-use interview guide template - [journey-map-workshop.md](references/journey-map-workshop.md) — Workshop facilitation guide - [user-story-workshop-guide.md](references/user-story-workshop-guide.md) — User story writing workshop ## Related Skills - `ork:write-prd` — Translate research insights into structured product requirements - `ork:product-frameworks` — Full PM framework suite (business cases, prioritization, metrics, OKRs) --- **Version:** 1.0.0
© OrchestKit · MIT · yonatangross/orchestkit
Similar skills
All skills for Design →user-research by other authors comes first.