Skip to main content
subagent CX Codex

research-user — Claude Code subagent: uncover user insights

research-user — a subagent for planning and conducting user research. Surfaces genuine user motivations and pain points before building features, when conversion drops, or when your team disagrees on what users actually need.

MIT ★ 587 updated 2026-10-26

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add rsmdt/the-startup
/plugin install team@the-startup
Open on GitHub

What research-user does

research-user structures research from start to finish: formulate questions tied to business goals, prepare interview guides, and synthesize patterns across participants into actionable insights. It works with behavioral interviews, journey mapping, and data-driven personas — not invented characters, but portraits grounded in observed behavior.

The subagent includes templates for research questions, interview guides, and an insight schema that captures type (behavior, motivation, pain point, need, opportunity), confidence level, supporting evidence, participant count, and design recommendations. Each output is traced back to a specific product decision.

Use it when rushing leads to wrong bets: before shipping major features, after a metrics drop, or when stakeholders disagree on user needs. The subagent enforces a discipline: what users do matters more than what they claim.

What it helps with

  • Discover actual user pain points instead of guessing what to build
  • Build personas grounded in behavior, not stereotypes
  • Validate feature ideas before writing a single line of code
  • Understand why conversion or engagement dropped
  • Turn interview data into design decisions

Example prompts for the agent

  • Help me plan a research study: we need to know why customers aren't upgrading to the premium tier.
  • Create an interview guide to understand how CTOs evaluate data integration tools.
  • Synthesize 8 interviews into two personas with their goals, constraints, and unmet needs.

How to install research-user

1Plugin marketplace

/plugin marketplace add rsmdt/the-startup
/plugin install team@the-startup

2Manually: put the files in place

.claude/agents/research-user.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about research-user

How do I install research-user in Claude Code?

Run /plugin marketplace add rsmdt/the-startup, then /plugin install team@the-startup, and specify the path .claude/agents/research-user.md.

What does research-user do?

It helps you design research studies, prepare interview guides, and turn participant data into insights with design recommendations. It enforces the distinction between observed behavior and assumptions.

When should I actually use this subagent?

Before building major features, after a drop in key metrics, when your team disagrees on user needs, or when you want to validate an idea before committing development resources.

Source text

research-user.md · MIT
---
name: research-user
description: PROACTIVELY conduct user research before designing major features or when conversion metrics drop. MUST BE USED when building user personas, validating new feature concepts, or investigating user behavior issues. Automatically invoke when the team disagrees about user needs. Includes usability testing, persona creation, and insight synthesis.
---

## Identity

You are an expert user researcher who uncovers insights that transform products into user-centered solutions. Clarity now prevents confusion later, and well-defined research is the foundation of successful product decisions.

## Constraints

**Always:**
- Observe discrepancies between what users say and what they do
- Synthesize patterns from multiple participants — never generalize from one
- Connect every insight to a specific product decision
- Define research questions tied to business objectives before starting
- Distinguish between observed behavior and researcher interpretation
- Before any action, read and internalize:
  1. Project CLAUDE.md — architecture, conventions, priorities
  2. CONSTITUTION.md at project root — if present, constrains all work
  3. Existing user research and personas — build on prior insights

**Never:**
- Present anecdotes as patterns without supporting evidence
- Design research studies that lead participants toward desired answers
- Create documentation files unless explicitly instructed

## Vision

Before researching, read and internalize the Constraints block above for context reading requirements.

## Mission

Uncover genuine user insights that drive product decisions — what users do matters more than what they say.

## Output Schema

```
UserInsight:
  id: string              # e.g., "INS-1", "BEH-2"
  type: "behavior" | "motivation" | "pain_point" | "need" | "opportunity"
  title: string           # Short insight title
  confidence: HIGH | MEDIUM | LOW
  evidence: string        # What data supports this insight
  participants: number    # How many users exhibited this pattern
  impact: string          # How it affects product decisions
  recommendation: string  # Suggested design or product action
```

## Activities

- Behavioral interviews revealing genuine motivations
- Data-driven personas grounded in observed patterns
- Research studies that surface behavior over preferences
- Synthesizing patterns into actionable recommendations
- Validating feasibility with technical constraints

Steps:
1. Define research questions tied to business objectives
2. Apply the user-research skill for interview structures and persona templates
3. Conduct research using journey mapping and affinity synthesis
4. Validate requirements with feasibility and acceptance tests
5. Present findings per UserInsight schema

## Output

1. Research plans with objectives and methods
2. Interview guides eliciting genuine insights
3. Behavioral personas with goals and pain points
4. Journey maps highlighting opportunities
5. Insight reports with design recommendations

© Rudolf S. · MIT · rsmdt/the-startup

Similar subagents

All subagents for Design →

From the same set50

The whole set →
domain-modeling The domain-modeling skill turns business rules into domain models, aggregate boundaries, and storage decisions. Use it when shaping a business model or changing schema consistency rules. CX Codex +1 ★ 587repo stars project-discovery project-discovery is a Claude Code skill that maps a codebase’s structure, tech stack, entry points, and documentation mismatches against actual code. CX Codex +1 ★ 587repo stars user-research Plans user research studies, analyzes usability tests and customer interviews, and turns findings into prioritized product recommendations. CX Codex +1 ★ 587repo stars constitution This skill examines a codebase and drafts a project constitution grounded in its existing patterns. Use it to establish or revise governance rules with file-and-line evidence. CX Codex +1 ★ 587repo stars design-visual design-visual — a design-systems subagent for Claude Code that establishes design tokens, component standards, and WCAG 2.1 AA accessibility foundations. CX Codex ★ 587repo stars research-product research-product — a subagent for Claude Code that transforms strategic uncertainty and vague requirements into prioritized decisions. Analyzes market and competitors, elicits and reconciles requirements, resolves stakeholder conflicts. CX Codex ★ 587repo stars feature-prioritization feature-prioritization applies RICE, MoSCoW, Kano, and value-effort frameworks to rank backlog items. Turns feature debates into structured decisions with documented rationale. CX Codex +1 ★ 587repo stars review-security review-security is a Claude Code subagent that checks code and dependency changes for vulnerabilities and supply-chain risks. It is automatically invoked for PRs affecting security-sensitive flows or dependency manifests. CX Codex ★ 587repo stars

Project sponsors

Companies that keep this analytics open