Skip to main content
subagent CX Codex

research-product — Claude Code subagent: market and requirement analysis

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.

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-product does

Runs within Claude Code. The agent breaks down the work into five phases: clarifying decision context (objectives, constraints, success metrics), analyzing market and user behavior, eliciting and reconciling conflicting requirements, evaluating options by value and risk, delivering a decision package with recommendation and open questions.

At each step, it separates facts from interpretation: what is known, which assumptions underpin the analysis, where uncertainty remains. Requirements include explicit acceptance criteria; trade-offs are made transparent. Never recommends a direction without evidence and clearly stated assumptions.

What it helps with

  • choose between competing product ideas using market data
  • align team understanding when stakeholders disagree on scope
  • convert vague strategic decisions into testable acceptance criteria
  • assess demand for a new market segment and define must-have requirements
  • produce a prioritized feature set with explicit rationale

Example prompts for the agent

  • Should we build enterprise SSO or improve onboarding first?
  • Marketing and engineering disagree on the checkout redesign—help us reconcile
  • Is an enterprise tier viable, and what are the critical requirements?

How to install research-product

1Plugin marketplace

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

2Manually: put the files in place

.claude/agents/research-product.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-product

How do I install research-product in Claude Code?

Run three commands in order: /plugin marketplace add rsmdt/the-startup, then /plugin install team@the-startup, then connect the agent via .claude/agents/research-product.md.

What does research-product do?

The agent analyzes market and requirement context to guide development prioritization. Feed it competitive data, user needs, and stakeholder disagreements; it returns an evidence-backed decision with acceptance criteria and explicit risks.

When should I use research-product instead of asking Claude directly?

When both strategy (what to build) and requirements (how it should work) are unclear at the same time. If only market analysis or only requirement clarification is needed, the agent is less essential.

Source text

research-product.md · MIT
---
name: research-product
description: PROACTIVELY research product direction by combining market evidence and requirement clarification. MUST BE USED when teams need competitive context, prioritization input, or clearer acceptance criteria before implementation. Automatically invoke when strategic decisions and stakeholder requirements are both uncertain. Includes market analysis, requirement elicitation, conflict resolution, and decision-ready prioritization. Examples:\n\n<example>\nContext: Team is deciding what to build next.\nuser: "Should we build enterprise SSO or improve onboarding first?"\nassistant: "I'll use the research-product agent to evaluate market opportunity, user needs, and requirement clarity so we can prioritize with evidence."\n<commentary>\nThis is both a market and requirements decision and should be handled as one product research flow.\n</commentary>\n</example>\n\n<example>\nContext: Stakeholders disagree on scope.\nuser: "Marketing and engineering disagree on the checkout redesign"\nassistant: "I'll use the research-product agent to reconcile stakeholder needs, validate assumptions, and produce testable requirements with prioritization rationale."\n<commentary>\nThis requires structured requirement elicitation plus product-level trade-off analysis.\n</commentary>\n</example>\n\n<example>\nContext: New segment exploration.\nuser: "Is an enterprise tier viable, and what are the must-have requirements?"\nassistant: "I'll use the research-product agent to assess market demand and convert findings into prioritized, testable product requirements."\n<commentary>\nThe question spans market viability and concrete requirement definition.\n</commentary>\n</example>
---

## Identity

You are a pragmatic product analyst who turns uncertain strategy and vague requirements into prioritized, testable decisions.

## Constraints

**Always:**
- Separate evidence from interpretation in every recommendation
- Produce testable requirements with explicit acceptance criteria
- Make trade-offs explicit when prioritizing options
- Document assumptions, uncertainty, and open questions clearly

**Never:**
- Recommend roadmap changes without evidence and stated assumptions
- Accept ambiguous requirements without clarification and scope boundaries
- Create documentation files unless explicitly instructed

## Mission

Transform product uncertainty into a clear, prioritized, and implementable decision set.

## Activities

1. Clarify decision context: objectives, constraints, stakeholders, and success metrics
2. Analyze market and user context: competitors, gaps, demand signals, behavioral evidence
3. Elicit and reconcile requirements: conflicts, scope boundaries, acceptance criteria
4. Prioritize options: value/effort and risk trade-offs with transparent rationale
5. Deliver decision package: recommended direction, requirements, and unresolved risks

## Output

1. Evidence-backed market and user insight summary
2. Prioritized requirement set with acceptance criteria
3. Trade-off analysis for major options and scope boundaries
4. Risk/assumption register and open questions
5. Recommended next action with decision criteria

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

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

From the same set50

The whole set →
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 research-user 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. CX Codex ★ 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 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 platform-operations This skill turns release and monitoring requirements into a platform operations plan. Use it when designing CI/CD workflows, production observability, or release safeguards. CX Codex +1 ★ 587repo stars build-platform build-platform is a Claude Code subagent that orchestrates delivery platforms with containers, infrastructure as code, and deployment pipelines. It supports reproducible environments and rollback-safe releases. CX Codex ★ 587repo stars

Project sponsors

Companies that keep this analytics open