产品开发三层思维

SKILL商业运营
商业运营 未标注权限 许可证不明确
安装这个技能

三层思维方法论: 发散性思维 — 不问"能不能卖",而问"用户生活里拿它解决什么问题"。把商品名拆成用户目的网络,沿着动作链延伸到关联产品,最终产出一张需求地图。停止标准:能说清"谁,在什么场景下,为了什么目的,愿意为什么差异付钱"。 收敛思维 — 五道关评估(需求稳定性 / 竞争烈度 / 利润空间 / 风险合规 / 资源匹配),把模糊机会压缩成一个可测试、可被推翻的选品假设。 反推逻辑 — 从终点倒推:产品本质是什么 → 需要哪些能力 → 还有什么供应链能满足同样目的。典型案例如茶叶罐重新定义为宠物骨灰盒,但必须满足功能匹配、情绪可表达、用户理解成本低三条规则。 三层可循环迭代:发散找到方向 → 收敛判断可行性 → 反推重新定义产品形态 → 再回到收敛验证。

一句话选型结论

按资料字段整理

产品开发三层思维是商业运营类的 Agent Skill,安装方式未标注,权限级别未标注,许可证不明确,有可直接复制的安装命令。技能本质是给模型读的说明书,效果取决于模型与客户端;装完先用一个小任务验证,再放进正式流程。

分类商业运营 安装方式未标注 权限级别未标注权限 许可证许可证不明确
累计安装 未标注 本周 未标注
GitHub 星标 未标注 仓库 未标注
下载量 未标注 技能市场下载数
权限级别 未标注权限 安装前请确认风险范围
许可证 许可证不明确 未说明

安装

未标注
在支持 Skills 的客户端里执行,装完问一句「你有哪些技能」验证
skillhub install user_05fc2940/product-development
  1. 1
    确认客户端支持

    确认你的客户端支持 Skills(Claude、Codex、Cursor 等),并升级到较新的版本。

  2. 2
    拿到技能文件

    执行上面的命令安装;也可以把仓库里的 SKILL.md 手动放进客户端的 skills 目录。

  3. 3
    刷新技能列表

    重新打开客户端,或刷新技能列表,让新放进来的技能被加载。

  4. 4
    验证是否生效

    问一句「你有哪些技能」,确认列表里出现它,再拿一个小任务试跑。

技能档案

商业运营
字段来自技能仓库与公开索引,中文说明由本站标注
作者 / 维护方user_05fc2940仓库 未标注 · 版本 未标注
宿主客户端未标注技能可被这些客户端加载
安装方式未标注安装包 community
权限级别未标注权限安装前请确认风险范围
许可证未说明许可证不明确,商用前请自行确认条款
仓库可用性available技能仓库当前是否可访问
最近核验未标注上游最后核验时间 · 数据更新 1791679732
正文体量13.2 KBSKILL.md 原文大小,越大说明说明书写得越细

典型使用场景

3 类
按分类整理的常见用法,具体以 SKILL.md 为准
写运营方案

按目标产出活动方案与执行清单。

分析数据与指标

从报表里找问题、给结论。

整理客户与销售材料

把客户信息与话术整理成可直接用的材料。

选择建议

装之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有可直接复制的安装命令,不用自己翻文档找入口。

先想清楚的地方

  • 没有标注权限级别,实际能做什么要装好后确认。
  • 许可证不明确,商用或二次分发前先到仓库确认条款。
  • 没有做站内核验,内容以作者仓库为准。
  • 技能只是说明书,实际效果取决于模型与客户端,装完先用小任务试一遍。

更适合

  • 需要在商业运营场景里给模型补一套做法的人。
  • 愿意先读一遍 SKILL.md、确认它会让模型做什么的人。

不太适合

  • 对许可证要求很严、必须明确可商用的人。
  • 只想装完就自动变强、不打算看说明书的人。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
技能权限级别安装方式累计安装宿主客户端安装命令
产品开发三层思维当前 未标注权限 未标注 未标注 未标注 有
MX 股票筛选器 联网访问 ClawHub 市场 79.9 万 OpenClaw 有
交易 未标注权限 ClawHub 市场 58.1 万 OpenClaw 有
营销技巧 只读 ClawHub 市场 54.0 万 OpenClaw 有
百灵鸟好 联网访问 GitHub 仓库 52.6 万 Codex、Claude、Cursor 有
股票信息浏览器 接触敏感数据 ClawHub 市场 40.5 万 OpenClaw 有

SKILL.md 全文

13.2 KB
模型实际读到的说明书原文,来自技能仓库

产品开发大师 (Product Development Master)

Overview

Product development for e-commerce (especially Amazon/cross-border) requires more than
tool-driven keyword research. A product direction, if wrong, cannot be fixed by Listing
optimization, ads, or keyword tuning later. This skill provides a three-layer thinking
methodology that connects demand understanding, feasibility evaluation, and product
redefinition into one coherent workflow.

The three layers are:

  1. Divergent Thinking (发散性思维) — Open up the demand world. Transform a product
    name into a network of user purposes and usage scenarios. Produce a demand map, not
    scattered keywords.
  2. Convergent Thinking (收敛思维) — Compress possibilities into testable plans. Pass
    each opportunity through five evaluation gates: demand, competition, profit, risk, and
    resource matching. Output a falsifiable hypothesis, not a conclusion.
  3. Reverse Logic (反推逻辑) — Redefine products from the endpoint. Ask what a product
    truly does for the user, then find alternative supply-chain solutions that fulfill the
    same essential purpose at a different price point or emotional value.

The three layers connect: divergent thinking finds product categories, markets, audiences,
and scenarios; convergent thinking determines whether an opportunity can enter execution;
reverse logic then loops back to the supply chain to find a better product form for the
validated demand.

When to Use

Activate this skill when the user:

  • Asks whether a product or category "can be done" (能不能做)
  • Requests product selection analysis (选品分析)
  • Wants to explore product opportunities or market gaps
  • Needs to evaluate a product direction's viability
  • Seeks differentiation angles for an existing product
  • Wants to redefine or reposition a product
  • Is researching demand for a new product line
  • Asks about sourcing strategy or supply chain alternatives

The Three-Layer Framework

Layer 1: Divergent Thinking

Goal: Transform a product name into a demand map of user purposes.

Core principle: Do not ask "can this product sell?" Ask "what problem does this solve
in the user's life?" A product name is just a label; the real opportunity lives in the
network of user purposes behind it.

Process summary:

  1. Start with a product name (e.g., "Christmas tree"). Do not look for products yet.
  2. Ask: what do users actually do with it? List all user purposes (decoration, ambiance,
    display, interaction, commercial use, modification, etc.).
  3. For each purpose, break down further: decorate what? how? for whom? Each branch leads
    to different audiences, keywords, image styles, and Listing language.
  4. Follow the action chain: what does the user do step by step? Each step points to
    associated products (tree topper, light strings, ribbons, ornaments, tree skirt,
    storage bag, hooks, display stand).
  5. Extend outward: if this scenario works, what adjacent scenarios share the same need?
  6. Source ideas from: reviews, TikTok, Quora, Instagram, X, Xiaohongshu, Taobao, 1688,
    offline stores, and real-life observations of how users use, complain about, modify,
    and combine products.

Stop criterion: Divergent thinking is complete when the following sentence can be
stated clearly for at least one opportunity:

> "Who, in what scenario, for what purpose, is willing to pay for what difference."

If this sentence cannot be constructed, the analysis is still circling keywords, not yet
in real demand territory.

Critical boundary: Divergence is not random brainstorming. Every idea must answer
three questions: who is the user, what is the scenario, and why would they pay. Ideas
that cannot answer these are just brainwaves, not opportunities.

For the full methodology, examples (Christmas tree case study), and the demand map
template, see references/divergent-thinking.md.

Layer 2: Convergent Thinking

Goal: Compress a validated demand opportunity into a testable, falsifiable hypothesis.

Core principle: Market demand only proves someone bought something similar. It does
not prove you can sell it, or that doing so now is worthwhile. Convergent thinking
transforms "I think this could work" into "I know why this is worth testing."

The five gates:

Gate Question Key checks
1. Demand Is the market stable? Search volume continuity, seasonal peaks, off-season baseline, trend direction
2. Competition Is it too crowded? Top listing review counts, 1000+ review listings count, brand concentration, image/selling-point homogenization, new listing viability
3. Profit Can costs and logistics sustain margin? Selling price, purchase cost, packaging upgrade, freight, FBA, platform commission, ad budget, return loss — all together, not just price vs. cost
4. Risk Are there legal/compliance landmines? Patents, trademarks, copyrights, certifications, material compliance, platform sensitive keywords — especially for distinctive shapes, patterns, IP, functional structures
5. Resource match Can current capabilities support this? Photography dependence, content capability, ad capability, inventory capacity — if the opportunity is real but current resources cannot support it, it is not for right now

Output: A selection hypothesis (选品假设) with the following structure:

  • Target audience: Who will buy
  • Usage scenario: When and where they use it
  • Core purpose: What problem they solve or feeling they seek
  • Differentiation source: Packaging, combination, material, size, function, visual, or content
  • Price logic: Why the user would pay this price for this difference
  • Validation actions: Test images first, test keywords, test small batch, or do competitor teardown and profit calculation first
  • Risk boundaries: At what ad cost, conversion rate, or unresolved IP risk to stop investing

For the full 5-gate evaluation framework, the Christmas scent gift set case study, and
the selection hypothesis template, see references/convergent-thinking.md.

Layer 3: Reverse Logic

Goal: Redefine products by working backwards from the user's essential purpose.

Core principle: A product is not what it is called; it is what it does for the user.
"Cat urn" is a label. Its essence is "a small, sealed, moisture-proof container with
memorial significance." Once the essence is extracted, alternative supply chains become
visible — a tea canister, with the right packaging and emotional layering, can enter the
pet memorial scenario.

Reverse logic process:

  1. Ask: what is this product's true purpose?
  2. Ask: what task is the user trying to complete by buying it?
  3. Ask: what functions, emotions, scenarios, and symbolic meanings are needed to fulfill
    that task?
  4. Ask: what other products can also satisfy these conditions?
  5. Evaluate: is the alternative supply chain more mature, cheaper, or more flexible?

Three rules for valid redefinition:

  1. Functional structure must match. A tea canister works for ashes because it is
    already sealed, moisture-proof, and small. If a product's structure has no connection
    to the new scenario, redefinition becomes forced labeling.
  2. Emotional value must be expressible. Pet memorial products sell not just containers
    but remembrance, farewell, preservation, and dignity. If images, packaging, and copy
    cannot express this, users see only a jar.
  3. User understanding cost must be low. A good redefinition lets users understand at a
    glance. If it requires lengthy explanation, the definition is too far from user
    cognition, and both advertising and conversion will struggle.

For the full methodology, the cat urn case study, and the redefinition checklist, see
references/reverse-logic.md.

Workflow

Apply the three layers in sequence, but allow iteration:

[User request: product idea or category]
         |
         v
+---------------------------+
| Layer 1: Divergent        |  Open up demand
| Thinking                  |  -> Demand map
+---------------------------+
         |
         v
+---------------------------+
| Layer 2: Convergent       |  Evaluate feasibility
| Thinking                  |  -> Selection hypothesis (5 gates)
+---------------------------+
         |
    Hypothesis viable?
    /              \
  Yes               No -> Back to Layer 1, try another branch
   |
   v
+---------------------------+
| Layer 3: Reverse Logic    |  Redefine product form
|                           |  -> Alternative supply chain
+---------------------------+
         |
         v
+---------------------------+
| Back to Layer 2 with      |  Re-evaluate the redefined product
| the redefined product     |  through the 5 gates
+---------------------------+
         |
         v
   Final output: actionable test plan

Step-by-step execution:

  1. Clarify the starting point. Determine whether the user has a specific product in
    mind, a category, or just a vague direction. If vague, help them narrow to a starting
    product name.

  2. Run divergent thinking. Build a demand map. List user purposes, break each into
    scenarios, follow action chains, and extend to adjacent needs. Stop when at least one
    opportunity can be stated as a complete demand sentence.

  3. Run convergent thinking. Take the most promising opportunity from the demand map
    and pass it through the 5 gates. Be honest — the goal is not to confirm a bias but to
    find out whether the opportunity is worth testing. Produce a selection hypothesis.

  4. Run reverse logic (if applicable). If the convergent thinking reveals that the
    obvious product form has issues (too competitive, too expensive, IP risk), use reverse
    logic to find alternative supply chain solutions that fulfill the same essential
    purpose.

  5. Loop back. Take the redefined product back through convergent thinking to validate
    the new form.

  6. Produce the final output. Deliver a structured document containing:
    - The demand map (key branches)
    - The selection hypothesis (all 7 elements)
    - The redefinition logic (if applied)
    - The next actions (what to test, what to verify, what to source)
    - The risk boundaries (when to stop)

Output Format

When producing analysis for the user, structure the output as:

Demand Map

Product: [name]
├── Purpose 1: [description]
│   ├── Scenario A: [who, where, why]
│   │   └── Action chain: [step 1 → step 2 → ...]
│   └── Scenario B: ...
├── Purpose 2: ...
└── Adjacent needs: [related products/scenarios]

Selection Hypothesis

Target audience:       [who]
Usage scenario:        [when, where]
Core purpose:          [what problem/feeling]
Differentiation source: [packaging/combination/material/size/function/visual/content]
Price logic:           [why pay this price]
Validation actions:    [test images / keywords / small batch / competitor teardown]
Risk boundaries:       [stop if ad cost > X, conversion < Y, IP risk unresolved]

Redefinition (if applied)

Original product:      [name]
Essential purpose:     [what it does for the user]
Required capabilities: [function, emotion, scenario, symbolism]
Alternative source:    [supply chain product]
Redefinition additions: [packaging, copy, visual changes]
Cost comparison:       [original vs. redefined]

Important Notes

  • Divergence without convergence is daydreaming. Convergence without divergence is
    copying. Both must happen.
  • The output of convergent thinking is a hypothesis, not a conclusion. It says "this
    is worth testing," not "this will sell."
  • Reverse logic is not relabeling. A cheap product cannot sell at a high price just by
    changing its name. The redefinition must genuinely solve the user's scenario problem or
    carry emotional value they are willing to pay for.
  • Tools validate thinking; they do not replace it. Keyword tools, market research
    tools, and supply chain platforms are for verification and supplementation. The demand
    map must exist in the mind first.
  • Surface-level opportunities are usually already taken. Real opportunities rarely
    float on top. Dig deeper into the demand map to find less obvious branches.

常见问题

5 问
答案由本站依据条目字段整理
产品开发三层思维怎么安装?

在支持 Skills 的客户端里执行:skillhub install user_05fc2940/product-development。安装方式为未标注。装完刷新技能列表或重开客户端。

产品开发三层思维支持哪些客户端?

资料没有标注宿主客户端,但只要客户端支持 Skills(Claude、Codex、Cursor 等),一般都能加载。

产品开发三层思维权限高吗,安全吗?

权限级别为未标注权限。安装前先看它会读取或写入哪些内容。

产品开发三层思维收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于技能本身和所用的模型或客户端,正式使用前按作者说明确认。

产品开发三层思维用什么许可证?

许可证标注为 未说明(许可证不明确)。商用或二次分发前请到仓库确认条款原文。

热门专题

按场景挑技能
全部专题 →

技能内容以作者仓库为准;分类、权限级别与许可证状态的中文说明为中文整理,最近核验 未标注。