phuryn/pm-skills

user-segmentation

Segment users from feedback data based on behavior, JTBD, and needs.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/phuryn/pm-skills --skill user-segmentation

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
phuryn
커뮤니티

strategy-red-team

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

1시간 설치 수
4
GitHub Stars
2.8만
업데이트
11월 8일
phuryn
커뮤니티

ansoff-matrix

Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.

1시간 설치 수
2
GitHub Stars
2.8만
업데이트
11월 8일
phuryn
커뮤니티

grammar-check

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.

1시간 설치 수
2
GitHub Stars
2.8만
업데이트
11월 8일
phuryn
커뮤니티

privacy-policy

Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.

1시간 설치 수
2
GitHub Stars
2.8만
업데이트
11월 8일