跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
其他技能

segment-market

Divide a venture's possible customers into demand situations that change a commercial decision, with recognition criteria and an evidence-based commercial profile. Use when the venture needs segments for the first time, when customer or market evidence changes, or when a target, opportunity or offer decision needs a clearer customer distinction. Writes the segments document.

LeanOS-Technologies · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add LeanOS-Technologies/strategy --skill segment-market

技能说明


name: segment-market description: Divide a venture's possible customers into demand situations that change a commercial decision, with recognition criteria and an evidence-based commercial profile. Use when the venture needs segments for the first time, when customer or market evidence changes, or when a target, opportunity or offer decision needs a clearer customer distinction. Writes the segments document.

segment-market

Transformation: customer-knowledge × market context × channel-map → segments.

The document follows its contract and the group's document rules.

When to use

  • Initial direction: candidate segments that define-differentiation and choose-targets will compare.
  • A new observation (a customer group behaving differently, a new alternative, a channel change) suggests the current boundaries no longer separate decisions.
  • A downstream skill reports that two targets or opportunities cannot be told apart, or that one segment hides two buying paths.

The question this skill answers: which differences between customers change what the venture should do, and how will anyone recognise a member?

Inputs and authority

InputUseAuthority
customer-knowledge (Evidence)Situations, jobs, triggers, alternatives, buying roles, with strength of supportEvidence owns the observations; this skill interprets them
market-landscape, market-size (Evidence)Alternatives and size factors where they existEvidence owns them
channel-map (Evidence)Where a segment can be reachedEvidence owns it
mandate (Governance), venture-definitionScope the segmentation must stay within; accepted customer breadthOwner and Governance
Owner materialWhat the owner states about customersQuote only what it contains
Product context (documentation, roadmap)Delivery differences that would split a segmentProduct owns capability

When Evidence documents do not exist yet, owner material and direct reasoning from the venture's situation supply the candidates. Proposed segments are legitimate work; they are labelled [proposed] and never attributed to a source that does not contain them. Population counts, demand and triggers that no source supports stay unknown.

Method

Record sources, exact owner quotes and calculation premises in the relevant table’s basis or source cells. Carry decision status in its status column and the document’s role; prose states choices and ambition directly.

1. Develop opportunities from direction and capabilities

Read the owner's purpose and ambition beside the venture's capabilities. Develop useful customer applications, including ones the owner did not list: who benefits, what becomes possible and how the venture could deliver it. Use those possibilities to frame the targeting, offer, channel and product decisions the segmentation must serve. Each boundary must change one of those decisions.

2. Recover situations, then group

Read the material for situations, not personas: circumstance, progress sought, current alternative, purchase conditions (demand situations and segment distinctions, "The unit of analysis is the situation"). Then group situations that would receive the same decision.

Notice especially:

  • Who buys versus who uses. A different buyer means a different purchase path, length and proof. This is the most frequent real boundary.
  • The trigger. A situation with a trigger (deadline, failure, growth step) buys; the same need without a trigger waits.
  • The alternative and its switching cost. Customers on paper and customers on a competing paid tool need different advantage chains.
  • Delivery differences. A team needs shared templates or administration that a single user does not; that changes offer scope.

Add candidate segments the material does not list when expertise suggests a consequential difference (customers on a competing tool; a sub-situation inside a slow segment that buys faster). Record the reason in Basis; the candidate document carries their proposed status.

3. Contrast neighbours and cut what does no work

For each segment, write how it differs from its nearest neighbour in trigger, buyer, alternative, delivery or value. If no difference changes a decision, merge them. Demographic or firmographic attributes stay only where they mark such a difference. Overlap is allowed; record it in Boundaries with its consequence.

4. Characterise demand and accessibility with the evidence there is

For each segment, fill the commercial profile from sources:

  • Demand and value: the indications relevant to this decision. Put the source of reported or observed demand in Basis; put the reasoning and strengthening action for an inferred need there.
  • Reach and purchasing: the channel, the decision-maker and the buying path (commercial accessibility and target choice, the accessibility chain). Name the link most likely to bind.
  • Size: a range from grounded factors, run through python3 workers/strategy/market-strategist/tools/market.py estimate FACTORS.csv, or unknown, or n/a: {reason} when the decision does not depend on it (evidence-sensitive comparison, "Estimates and ranges"). The tool returns unknown and names the missing factor when any factor lacks a basis; copy that result, never a guessed number.
  • Delivery: what serving the segment requires.

5. Test usability

For each segment ask: can Evidence recognise a member from the criteria? Can Engagement reach one? Can Product state what they need? Rewrite criteria that only the venture can see ("values our approach") as observable indicators, or mark them for

阅读完整来源 ↗