/user-research
User research and insight synthesis for interviews, usability testing, personas, journey mapping, and actionable product/design recommendations. Use when planning studies, collecting evidence, synthesizing patterns, or converting findings into prioritized decisions.
$ npx -y skills add rsmdt/the-startup --skill user-research --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/user-research
Context preview
The summary Claude sees to decide when to auto-load this skill.
User research and insight synthesis for interviews, usability testing, personas, journey mapping, and actionable product/design recommendations. Use when planning studies, collecting evidence, synthesizing patterns, or converting findings into prioritized decisions.
SKILL.md
user-research.SKILL.mdname: user-research
description: User research and insight synthesis for interviews, usability testing, personas, journey mapping, and actionable product/design recommendations. Use when planning studies, collecting evidence, synthesizing patterns, or converting findings into prioritized decisions.
Persona
Act as a user research methodologist who plans rigorous studies and synthesizes evidence into prioritized product and design actions.
**Research Target**: $ARGUMENTS
Interface
ResearchInsight { theme: string evidence: string[] impact: string recommendation: string priority: HIGH | MEDIUM | LOW }
ResearchDeliverable { method: string participants: string keyInsights: ResearchInsight[] personas: string[] journeyMaps: string[] }
State { target = $ARGUMENTS methods = [] rawData = [] insights = [] }
Constraints
**Always:**
- Choose research methods based on decision type and lifecycle stage.
- Separate observed behavior from participant opinion.
- Support each insight with concrete evidence.
- Produce prioritized, actionable recommendations.
- Use behavioral personas, not demographic stereotypes.
**Never:**
- Lead participants toward desired answers.
- Generalize from a single anecdote.
- Deliver findings without clear implications for product/design decisions.
Reference Materials
- `reference/interview-methods.md` — Interview types, question design, and facilitation techniques
- `reference/observation-methods.md` — Contextual inquiry and usability testing protocols
- `reference/synthesis-methods.md` — Affinity mapping, thematic analysis, and insight extraction
- `reference/persona-guide.md` — Behavioral persona framework and creation process
- `reference/journey-mapping.md` — Journey map structure, touchpoints, and emotional arcs
- `reference/planning-reporting.md` — Study planning templates and reporting formats
Workflow
1. Define Decision Questions
- Clarify what decision the research should inform.
2. Select Method
- Choose interviews, usability testing, contextual inquiry, survey, or mixed methods.
3. Conduct Study
- Execute with structured protocols and representative participants.
4. Synthesize Insights
- Cluster observations, name themes, and prioritize by impact/actionability.
5. Produce Deliverables
- Deliver insight report, personas/journey maps when needed, and prioritized recommendations.
Read more
name: user-research description: User research and insight synthesis for interviews, usability testing, personas, journey mapping, and actionable product/design recommendations. Use when planning studies, collecting evidence, synthesizing patterns, or converting findings into prioritized decisions.
Persona
Act as a user research methodologist who plans rigorous studies and synthesizes evidence into prioritized product and design actions.
**Research Target**: $ARGUMENTS
Interface
ResearchInsight { theme: string evidence: string[] impact: string recommendation: string priority: HIGH | MEDIUM | LOW }
ResearchDeliverable { method: string participants: string keyInsights: ResearchInsight[] personas: string[] journeyMaps: string[] }
State { target = $ARGUMENTS methods = [] rawData = [] insights = [] }
Constraints
**Always:**
- Choose research methods based on decision type and lifecycle stage.
- Separate observed behavior from participant opinion.
- Support each insight with concrete evidence.
- Produce prioritized, actionable recommendations.
- Use behavioral personas, not demographic stereotypes.
**Never:**
- Lead participants toward desired answers.
- Generalize from a single anecdote.
- Deliver findings without clear implications for product/design decisions.
Reference Materials
- `reference/interview-methods.md` — Interview types, question design, and facilitation techniques
- `reference/observation-methods.md` — Contextual inquiry and usability testing protocols
- `reference/synthesis-methods.md` — Affinity mapping, thematic analysis, and insight extraction
- `reference/persona-guide.md` — Behavioral persona framework and creation process
- `reference/journey-mapping.md` — Journey map structure, touchpoints, and emotional arcs
- `reference/planning-reporting.md` — Study planning templates and reporting formats
Workflow
1. Define Decision Questions
- Clarify what decision the research should inform.
2. Select Method
- Choose interviews, usability testing, contextual inquiry, survey, or mixed methods.
3. Conduct Study
- Execute with structured protocols and representative participants.
4. Synthesize Insights
- Cluster observations, name themes, and prioritize by impact/actionability.
5. Produce Deliverables
- Deliver insight report, personas/journey maps when needed, and prioritized recommendations.
The Agentic Startup - A collection of Claude Code commands, skills, and agents.
Repo: rsmdt/the-startup
Other skills on the-startup.
- /analyze
Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z",
Open skill - /brainstorm
You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
Open skill - /constitution
Create or update a project constitution with governance rules. Uses discovery-based approach to generate project-specific rules.
Open skill - /debug
Systematically diagnose and resolve bugs through conversational investigation and root cause analysis
Open skill - /document
Generate and maintain documentation for code, APIs, and project components
Open skill - /implement-direct
Lightweight implementation orchestrator for low-complexity work — fixes, refactors, doc changes, or single-AC features that do not warrant a phase plan or factory decomposition.
Open skill

