From product-builder
Use when user explicitly wants market research, competitor analysis, or needs help deciding what product to build. Triggers: "do market research", "analyze competitors", "what should I build", "validate this idea", "is there a market for". Do NOT trigger for casual product discussions or when user already has clear requirements.
How this skill is triggered — by the user, by Claude, or both
Slash command
/product-builder:pm-market-researchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Help product builders discover and validate product opportunities through market research.
Help product builders discover and validate product opportunities through market research.
Use WebSearch and WebFetch based on what you need:
| Need | Method | Example |
|---|---|---|
| Find pain points | WebSearch | "frustrated with X" reddit, "I wish there was" HackerNews |
| Discover trends | WebSearch | trending products on Product Hunt, GitHub trending |
| Analyze competitors | WebFetch | competitor pricing pages, feature lists |
| Understand users | WebSearch | user discussions, reviews, complaints |
| Validate market | WebSearch + WebFetch | market reports, industry analysis |
Note: All research uses publicly available web sources.
Focus on small and beautiful, not large and comprehensive:
Why this matters:
Use brainstorming skill when exploring ideas to ensure focus on user pain points and small-beautiful approach.
Gather three pieces of context before researching:
How to gather: Check what's already clear from user's message, then ask about missing pieces in a single question. Example: user says "I want to build a subscription manager to make money" → direction and goal are clear, only ask about target market.
DO NOT proceed to research until all three are confirmed. Goal and Market determine which competitors to analyze, what pricing to reference, and which trends are relevant.
Based on whether user has a direction:
Purpose: Discover potential directions (breadth). This step identifies options—detailed validation happens in Step 3.
Help user find direction through trend research:
Use WebSearch to discover:
Present 2-3 potential directions with:
Wait for user to confirm direction, then proceed to Step 3 (Deep Dive).
Purpose: Validate the chosen direction (depth). This step provides thorough analysis to inform the PRD.
Research the selected direction thoroughly:
Competitor Analysis:
User Research:
Market Opportunity:
Generate docs/prd/research-<topic>.md:
# <Topic> Market Research
## Goals & Background
- Purpose: [user's goal]
- Constraints: [if any]
## Market Opportunity
- Market overview
- Trends and timing
- Why now
## Competitor Analysis
| Competitor | Strengths | Weaknesses | Pricing |
|------------|-----------|------------|---------|
| ... | ... | ... | ... |
### User Pain Points with Competitors
- [Competitor A]: [common complaints, missing features]
- [Competitor B]: [common complaints, missing features]
## Target Users & Pain Points
- Primary persona
- Core pain points
- Current workarounds
## Recommended Direction
- Suggested approach
- Differentiation strategy
- Rationale
After generating the document, suggest: "Want to dive deeper into competitor features? Use /pm-competitor-analysis for detailed analysis. Or skip to /pm-prd if ready to define requirements."
npx claudepluginhub sparktech-ai/skills --plugin product-builderResearches markets via interactive questioning on scope, then deploys parallel agents for trend analysis, consumer insights, competitive landscape, size estimates (TAM/SAM/SOM), and go/no-go recommendations.
Runs initial market research, updates findings, and answers questions about market size, customer segments, buying behavior, pricing benchmarks, and industry trends for startup founders.
Analyzes competitive landscape for your product: identifies 5 direct competitors, profiles strengths/weaknesses/pricing/GTM, maps differentiation opportunities. Use for market research or briefs.