customer-segment-slicing
Narrow broad customer categories into specific, reachable who-where segments for customer discovery, positioning, traction tests, sales outreach, or SEO personas. Use when feedback is inconsistent, the market is too broad, personas are vague, users request too many different features, or the team does not know where to find target customers.
- License 许可
- MIT
- 最近更新
- 2026-06-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- customer-segment-slicing
- license
- MIT
- metadata
- { "tags": "customer-discovery,segmentation,startups,positioning,research", "version": "0.1.3", "category": "Marketing", "displayName": "Customer Segment Slicing" }
- description
- Narrow broad customer categories into specific, reachable who-where segments for customer discovery, positioning, traction tests, sales outreach, or SEO personas. Use when feedback is inconsistent, the market is too broad, personas are vague, users request too many different features, or the team does not know where to find target customers.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 2
- 参考文档agents/openai.yaml223 B
- 参考文档workflows/slice-customer-segment.md1.3 KB
03 SKILL.md 正文
Customer Segment Slicing
Use this skill before customer conversations, traction tests, sales outreach, or persona work when the target customer is too broad to produce consistent evidence. A useful segment is a who-where pair: who has the problem and where the team can find them.
Source Traceability
Primary source: The Mom Test by Rob Fitzpatrick, especially chapters 6-7. Guidance is paraphrased for this MIT repo; authoring notes used converted EPUB lines 2791-3610.
Slicing Workflow
- Start with the broad audience or market.
- Split by demographics, role, use case, behavior, buying context, urgency, or current workaround.
- For each slice, state the motivation or problem that makes them care.
- Keep slicing any group that still produces mixed goals or feature requests.
- Add where to find each group: communities, events, tools, platforms, job titles, search queries, partners, directories, or physical locations.
- Score the slices by reachability, expected value, urgency, consistency, and team fit.
- Pick one starting segment for the next discovery or traction pass.
Useful Segment Tests
Ask:
- Would most people in this slice share the same problem or goal?
- Can we find at least five of them this week?
- Do they already spend time, money, attention, or reputation on this problem?
- Would their feedback point toward one product direction rather than many?
- Are there hidden stakeholders, buyers, users, or partners?
- Is this slice narrow enough to learn from but valuable enough to matter?
Output Format
# Customer Segment Slicing
## Broad Segment
[Starting audience.]
## Candidate Slices
| Segment | Problem or Goal | Where To Find Them | Current Behavior | Reachability | Value | Urgency | Consistency | Fit |
|---------|-----------------|--------------------|------------------|--------------|-------|---------|-------------|-----|
## Recommended Starting Segment
[One who-where pair.]
## Why This Segment
- Strong shared motivation:
- Easy access path:
- Evidence to gather:
- Risks:
## Next Conversations
1. [Person/source]
2. [Person/source]
3. [Person/source]
Workflow
Use workflows/slice-customer-segment.md for a full segmentation pass.
Quality Bar
- Do not accept categories like "students", "businesses", or "creators" without further slicing.
- Do not optimize positioning or features from mixed-segment feedback.
- Do not choose a segment that cannot be found.
- Do not talk only to impressive people if they are not representative users, buyers, or stakeholders.
04 同仓库更多 Skills
android-emulator-qa
Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.
supabase-postgres-best-practices
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
sentry
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
render-workflows
Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.
render-web-services
Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.
render-static-sites
Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React/Vue/Hugo/Gatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.