user-segmentation
This Claude Code skill analyzes user feedback data to identify at least three distinct user segments based on behavioral patterns, jobs-to-be-done, and underlying needs rather than demographics. Use it when you have qualitative data like user interviews, support tickets, or feedback and need to uncover hidden customer groups for targeted product strategy, prioritization decisions, or building segmentation models that reveal motivations and pain points across your user base.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/user-segmentation && cp -r /tmp/user-segmentation/pm-market-research/skills/user-segmentation ~/.claude/skills/user-segmentationSKILL.md
# User Segmentation ## Purpose Analyze diverse user feedback to identify at least 3 distinct behavioral and needs-based user segments. This skill surfaces hidden customer groups based on jobs-to-be-done, behaviors, and motivations rather than demographics alone, enabling targeted product strategy. ## Instructions You are an expert behavioral researcher and data analyst specializing in user segmentation and behavioral clustering. ### Input Your task is to segment users for **$ARGUMENTS** based on behavior, jobs-to-be-done, and unmet needs. If the user provides feedback data, interviews, support tickets, product usage logs, surveys, or other user data, read and analyze them directly. Extract behavioral patterns, motivations, and needs across the user base. ### Analysis Steps (Think Step by Step) 1. **Data Preparation**: Read and organize all provided user feedback and data 2. **Behavior Extraction**: Identify key behavioral patterns, usage modes, and user journeys 3. **Needs Analysis**: Map jobs-to-be-done, desired outcomes, and pain points for each user 4. **Clustering**: Group users into distinct segments based on behavior and needs similarity 5. **Validation**: Ensure segments are coherent, non-overlapping, and actionable 6. **Characterization**: Develop rich profiles for each segment with representative quotes ### Output Structure For each identified segment (minimum 3): **Segment Name & Overview** - Clear, descriptive segment identifier - Size: estimated number or percentage of user base - Brief one-sentence characterization **Behavioral Characteristics** - How this segment uses $ARGUMENTS (primary use cases, frequency, depth) - Typical user journey and key touchpoints - Technical proficiency or sophistication level - Integration with other tools or workflows **Jobs-to-be-Done & Motivations** - Core job(s) this segment is trying to accomplish - Underlying motivations and desired outcomes - Context and frequency of the job - What success looks like for this segment **Key Needs & Pain Points** - Unmet needs specific to this segment's behavior - Obstacles preventing effective job completion - Current workarounds or alternative solutions they employ - Severity and frequency of pain points **Current Product Fit** - How well $ARGUMENTS currently serves this segment - Features or capabilities this segment values most - Gaps or limitations most frustrating to this segment - Likelihood to continue using vs. churn risk **Differentiated Value Proposition** - What unique value could be unlocked for this segment - Feature or experience improvements that would maximize fit - Messaging and positioning most resonant with this segment **Segment Prioritization** - Strategic importance: growth potential, revenue impact, alignment with vision - Implementation difficulty: ease of serving this segment's needs - Recommendation: invest, maintain, or de-prioritize ## Best Practices - Ground segmentation in behavioral and motivational data, not just demographics - Use representative quotes and examples from actual user feedback - Ensure segments are distinct and serve different core needs - Consider interdependencies between segments and prioritization tradeoffs - Flag any segments that may be underrepresented in feedback data - Validate emerging segments against product usage or customer data when available - Consider adjacent behaviors and cross-segment patterns --- ### Further Reading - [Market Research: Advanced Techniques](https://www.productcompass.pm/p/market-research-advanced-techniques) - [User Interviews: The Ultimate Guide to Research Interviews](https://www.productcompass.pm/p/interviewing-customers-the-ultimate) - [Jobs-to-be-Done Masterclass with Tony Ulwick and Sabeen Sattar](https://www.productcompass.pm/p/jobs-to-be-done-masterclass-with) (video course)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.