market-segments
Identify 3-5 potential customer segments with demographics, JTBD, and product fit analysis. Use when exploring market segments, identifying target audiences, evaluating new markets, or learning how to segment a market.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-06
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- market-segments
- description
- Identify 3-5 potential customer segments with demographics, JTBD, and product fit analysis. Use when exploring market segments, identifying target audiences, evaluating new markets, or learning how to segment a market.
03 SKILL.md 正文
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
04 同仓库更多 Skills
tb-writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
tb-using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
tb-test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
tb-subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
tb-scrutinize
Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler/more elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and every call carries its rationale. Trigger on /tb-scrutinize and proactively whenever the user asks to review, audit, sanity-check, or get a second opinion on a plan, PR, diff, design doc, or proposed code change.
tb-requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements