market-segments▌
phuryn/pm-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Identify and analyze 3-5 distinct customer segments for your product, understanding their unique jobs-to-be-done, desired outcomes, pain points, and product fit. Use this skill to evaluate market opportunities, prioritize target audiences, or expand into new market segments.
Market Segments
Purpose
Identify and analyze 3-5 distinct customer segments for your product, understanding their unique jobs-to-be-done, desired outcomes, pain points, and product fit. Use this skill to evaluate market opportunities, prioritize target audiences, or expand into new market segments.
Instructions
You are a strategic market research expert skilled in market segmentation, customer profiling, and total addressable market (TAM) analysis.
Input
Your task is to identify and analyze potential customer segments for $ARGUMENTS.
If research data, market studies, customer databases, or existing segmentation documents are provided, read and analyze them directly. Look for behavioral patterns, demographic clusters, and distinct needs across segments.
Analysis Steps (Think Step by Step)
- Market Exploration: Consider the full addressable market for $ARGUMENTS
- Segmentation Criteria: Identify logical segmentation dimensions (behavioral, demographic, firmographic, needs-based)
- Segment Definition: Create 3-5 distinct, non-overlapping customer segments
- Characterization: For each segment, synthesize profiles and validate distinctness
- Opportunity Assessment: Evaluate market size, growth potential, and competitive intensity per segment
Output Structure
For each of the 3-5 segments, provide:
Segment Name & Overview
- Clear, memorable segment identifier
- Size estimate (% of total market or absolute numbers if data available)
- Growth trajectory and market dynamics
Key Demographics & Firmographics
- Core characteristics (age, role, company size, industry, geography, etc.)
- Decision-maker profiles if B2B
Jobs-to-be-Done
- Primary job and desired outcome for this segment
- Frequency, context, and stakes of the job
- Success criteria and desired outcomes
Key Pain Points & Obstacles
- Barriers to job completion specific to this segment
- Consequences of not solving the problem
Desired Gains & Success Factors
- What outcomes matter most to this segment
- Preferred solution characteristics
- Cost and time constraints
Product Fit Analysis
- How well $ARGUMENTS serves this segment's needs
- Unique value proposition for this segment
- Potential adoption barriers or resistance
Competitive Landscape
- Existing solutions or workarounds this segment uses
- Alternative approaches or competitors
Best Practices
- Ensure segments are measurable, accessible, and distinct
- Prioritize segments with clear jobs-to-be-done and pain points
- Validate segment assumptions with available data
- Consider both greenfield opportunities and underserved segments
- Flag segments requiring additional market research
Further Reading
How to use market-segments on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add market-segments
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches market-segments from GitHub repository phuryn/pm-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate market-segments. Access the skill through slash commands (e.g., /market-segments) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.4★★★★★38 reviews- ★★★★★Ganesh Mohane· Dec 28, 2024
market-segments reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Isabella Dixit· Dec 24, 2024
We added market-segments from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Nia Bansal· Dec 16, 2024
Solid pick for teams standardizing on skills: market-segments is focused, and the summary matches what you get after install.
- ★★★★★Anaya Gonzalez· Nov 19, 2024
market-segments reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Chinedu Huang· Nov 15, 2024
Keeps context tight: market-segments is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Noah Shah· Nov 3, 2024
I recommend market-segments for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Anika Jain· Oct 22, 2024
Useful defaults in market-segments — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Harper Dixit· Oct 10, 2024
Registry listing for market-segments matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ama Rahman· Oct 6, 2024
market-segments is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Benjamin Mensah· Sep 25, 2024
Solid pick for teams standardizing on skills: market-segments is focused, and the summary matches what you get after install.
showing 1-10 of 38