mcpField
S
six-thinking-hats

six-thinking-hats

github.com/guia-matthieu生产力150249 次安装4 周前更新
代码仓库

关于 six-thinking-hats

six-thinking-hats 是一项 Claude 技能,运用 Edward de Bono 的六顶思考帽方法分析决策、评估和创意议题。它将讨论组织为六种共同视角,涵盖事实、风险、收益与替代方案。

主要功能

  1. 01六种视角的决策分析
  2. 02结构化评估提示词
  3. 03创意替代方案生成
  4. 04会议引导指南
  5. 05可复用分析模板

适用场景

  1. 01评估产品发布
  2. 02比较战略方案
  3. 03组织决策会议
  4. 04为停滞的问题构思替代方案

安装

复制下面的命令,在终端中运行。

$npx skills add https://github.com/guia-matthieu/clawfu-skills --skill six-thinking-hats

安装后在 Claude Code 中输入/six-thinking-hats确认已加载。

详细介绍

六顶思考帽

运用 Edward de Bono 于 1985 年提出的平行思维框架,从六种不同视角系统地审视想法,从而做出更好的决策。

何时使用此技能

  • 做出需要多种视角的复杂决策
  • 在推出之前评估新产品、优惠或策略
  • 通过结构化思考摆脱分析瘫痪
  • 开展高效会议,让所有人朝同一方向思考
  • 在战略规划中平衡乐观与谨慎
  • 在问题陷入僵局时提出创意替代方案

方法论基础

方面详情
来源六顶思考帽(1985 年)
专家Edward de Bono——“水平思考”一词的创造者,曾为 IBM、Shell、NASA 提供咨询
核心原则“平行思维”——所有人不再进行对抗式辩论,而是在同一时间朝同一方向思考,并一起切换视角

Claude 负责什么,你来决定什么

Claude 负责你来决定
构建内容框架最终文案
建议说服技巧品牌调性
创建草稿变体版本选择
识别优化机会发布时间
分析竞争对手的做法战略方向

此技能的作用

此技能用结构化平行思维取代混乱的头脑风暴和低效的辩论。

人们不再各自捍卫立场、攻击他人,而是一起:

  1. 审视事实(白帽)
  2. 分享感受(红帽)
  3. 探索风险(黑帽)
  4. 发现益处(黄帽)
  5. 提出替代方案(绿帽)
  6. 共同管理流程(蓝帽)

结果:更快做出决策、更容易达成共识、更具创意的解决方案,并减少冲突。

使用方法

分析决策或策略
Apply the Six Thinking Hats to analyze:
[describe decision, product, strategy, or problem]

Go through each hat systematically and provide insights.
开展结构化评估
I need to decide whether to [decision].
Walk me through Six Thinking Hats analysis with specific questions for each hat.
提出创意替代方案
Use Six Thinking Hats (focusing on Green Hat) to generate alternatives for:
[current approach or problem]
First establish context with White and Red, then expand with Green.

说明

六顶帽子概览
┌─────────────────────────────────────────────────────────────────┐
│                    THE SIX THINKING HATS                        │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  🎩 BLUE HAT    - Process & Control                             │
│     "What hat should we use now?"                               │
│                                                                 │
│  ⬜ WHITE HAT   - Facts & Information                           │
│     "What do we know? What don't we know?"                      │
│                                                                 │
│  ❤️ RED HAT     - Emotions & Intuition                          │
│     "What does my gut say? How do I feel?"                      │
│                                                                 │
│  ⚫ BLACK HAT   - Caution & Risks                               │
│     "What could go wrong? What are the dangers?"                │
│                                                                 │
│  💛 YELLOW HAT  - Benefits & Value                              │
│     "What are the benefits? Why will this work?"                │
│                                                                 │
│  💚 GREEN HAT   - Creativity & Alternatives                     │
│     "What else could we do? What's a new approach?"             │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

帽子 1:蓝帽(流程控制)
## 🎩 BLUE HAT - The Conductor

**Focus:** Managing the thinking process itself

**Role:** The Blue Hat is the "meta" hat - it controls which hat is used
when, keeps the group focused, and summarizes conclusions.

**When to Use:**
- At the START: Define the problem and set the agenda
- DURING: Switch hats, refocus discussion
- At the END: Summarize findings and next steps

**Blue Hat Questions:**
- What is the problem we're trying to solve?
- What outcome do we want from this thinking session?
- Which hat should we use next?
- Have we spent enough time on this perspective?
- What have we concluded so far?
- What are the next steps?

**Blue Hat Outputs:**
- Clear problem definition
- Thinking agenda (hat sequence)
- Time allocation per hat
- Summary of insights
- Action items and decisions

**Tip:** Start and end every session with Blue Hat.

帽子 2:白帽(事实与信息)
## ⬜ WHITE HAT - The Scientist

**Focus:** Objective facts, data, and information

**Role:** Neutral, factual thinking. No interpretations, no opinions.
Just "what do we know?" and "what do we need to find out?"

**When to Use:**
- Early in the process to establish baseline
- When debate gets heated (return to facts)
- Before making final decisions

**White Hat Questions:**
- What data do we have?
- What are the facts?
- What information is missing?
- How reliable is this information?
- What do the numbers say?
- What has happened in similar situations?

**White Hat Outputs:**
- List of known facts
- Data points and metrics
- Gaps in information
- Sources and reliability assessment
- Historical precedents

**Rules:**
- NO opinions ("I think..." = Red Hat)
- NO judgments ("That's bad..." = Black Hat)
- Just facts: "Sales were 10,000 units" ✓
- Flag uncertainty: "We believe X, but haven't verified"

**Example:**
❌ "The market is too competitive" (opinion)
✅ "There are 47 competitors. Top 3 have 60% market share." (fact)

帽子 3:红帽(情绪与直觉)
## ❤️ RED HAT - The Heart

**Focus:** Feelings, intuition, gut reactions

**Role:** Express emotions WITHOUT justification. No need to explain
why you feel something - just state the feeling.

**When to Use:**
- After establishing facts (gauge emotional response)
- When something "feels off" but can't be articulated
- To surface hidden concerns or excitement
- Before final decisions (gut check)

**Red Hat Questions:**
- How do you feel about this?
- What's your gut reaction?
- What excites you about this?
- What worries you (emotionally)?
- If you had to decide right now, what would you choose?
- What's your intuition saying?

**Red Hat Outputs:**
- Emotional reactions (positive and negative)
- Intuitive hunches
- Excitement levels
- Concern levels
- Gut-based preferences

**Rules:**
- NO justification required
- "I don't like it" is valid (no need for why)
- Feelings are data points, not arguments
- Everyone's feelings are legitimate
- Brief expressions (not long explanations)

**Example:**
✅ "I feel excited about this"
✅ "Something feels off, I'm not sure what"
✅ "My gut says we should wait"
❌ "I feel this won't work because the market is saturated" (that's Black Hat)

帽子 4:黑帽(谨慎与风险)
## ⚫ BLACK HAT - The Judge

**Focus:** Caution, risks, problems, what could go wrong

**Role:** Critical thinking - identify weaknesses, dangers, and flaws.
This is NOT negativity for its own sake, but protective thinking.

**When to Use:**
- After Yellow Hat (balance optimism with caution)
- Before committing resources
- To stress-test ideas
- To identify what needs mitigation

**Black Hat Questions:**
- What could go wrong?
- What are the risks?
- What are the weaknesses?
- Why might this fail?
- What obstacles will we face?
- What are the costs and downsides?
- Does this fit with our resources/capabilities?
- What have we overlooked?

**Black Hat Outputs:**
- List of risks and dangers
- Potential failure modes
- Resource constraints
- Logical flaws in the plan
- External threats
- Implementation challenges

**Rules:**
- Must be LOGICAL (not just feelings - that's Red)
- Point to specific risks, not vague negativity
- "This could fail because X" ✓
- "I just don't like it" ✗ (that's Red Hat)

**The Black Hat is VALUABLE:**
- Prevents disasters
- Identifies what needs fixing
- Ensures realistic planning
- Required before any major decision

**Example:**
✅ "If competitors copy this in 3 months, we lose first-mover advantage"
✅ "Our team has never done X before - execution risk is high"
❌ "This will never work" (too vague)

帽子 5:黄帽(益处与价值)
## 💛 YELLOW HAT - The Optimist

**Focus:** Benefits, value, why it will work

**Role:** Constructive, positive thinking. Find the value and benefits.
Look for what's good about an idea.

**When to Use:**
- To explore the upside of ideas
- When team is too negative
- To build enthusiasm and motivation
- To find value in unexpected places

**Yellow Hat Questions:**
- What are the benefits?
- Why will this work?
- What's the best-case scenario?
- Who gains from this and how?
- What opportunities does this create?
- What's valuable about this idea?
- How can we make this succeed?

**Yellow Hat Outputs:**
- List of benefits
- Value propositions
- Success scenarios
- Opportunity identification
- Reasons for optimism
- Supporting evidence for success

**Rules:**
- Must have LOGICAL basis (not just hope)
- "This will work because X" ✓
- "I hope it works" ✗ (that's Red Hat)
- Find genuine benefits, not forced positivity

**Balance with Black Hat:**
Yellow without Black = naive optimism
Black without Yellow = paralysis
Both together = realistic assessment

**Example:**
✅ "If we capture 5% of the market, that's $2M revenue"
✅ "This positions us as thought leaders in an emerging space"
❌ "It'll be great!" (no substance)

帽子 6:绿帽(创意与替代方案)
## 💚 GREEN HAT - The Creator

**Focus:** New ideas, alternatives, creative solutions

**Role:** Generate possibilities without judgment. Explore "what if?"
Think beyond obvious solutions.

**When to Use:**
- When stuck on a problem
- After Black Hat identifies problems (find solutions)
- To generate options before deciding
- When current approach isn't working

**Green Hat Questions:**
- What alternatives exist?
- What if we did the opposite?
- How might we approach this differently?
- What would [successful company/person] do?
- What's a completely new way to solve this?
- How can we overcome the Black Hat concerns?
- What assumptions can we challenge?

**Green Hat Techniques:**
- **Random Entry:** Pick random word, connect to problem
- **Reversal:** What's the opposite approach?
- **Analogy:** How do other industries solve this?
- **Exaggeration:** What if we 10x'd this element?
- **Combination:** Merge two different approaches

**Green Hat Outputs:**
- List of alternative approaches
- Creative solutions
- New ideas to explore
- Modifications to existing ideas
- "What if" scenarios

**Rules:**
- NO judgment during Green Hat (judgment = Black)
- Quantity over quality initially
- Build on others' ideas ("Yes, and...")
- Suspend disbelief temporarily
- Wild ideas welcome (can be refined later)

**Example:**
✅ "What if we gave it away free and monetized differently?"
✅ "What if we partnered with competitors instead of fighting them?"
✅ "What if we targeted the opposite customer segment?"

推荐的帽子顺序
## Common Hat Sequences

### For EVALUATING an Idea:
1. 🎩 Blue   - Define what we're evaluating
2. ⬜ White  - Gather facts about the idea
3. ❤️ Red    - Initial gut reactions
4. 💛 Yellow - Explore benefits
5. ⚫ Black  - Identify risks
6. 💚 Green  - Generate improvements/alternatives
7. ❤️ Red    - Final gut check
8. 🎩 Blue   - Summarize and decide

### For SOLVING a Problem:
1. 🎩 Blue   - Define the problem clearly
2. ⬜ White  - Understand the facts
3. 💚 Green  - Generate solutions (many options)
4. 💛 Yellow - Evaluate benefits of each
5. ⚫ Black  - Evaluate risks of each
6. ❤️ Red    - Which feels right?
7. 🎩 Blue   - Choose and plan next steps

### For QUICK Decisions:
1. ⬜ White  - Key facts only (2 min)
2. ❤️ Red    - Gut reaction (1 min)
3. 💛 Yellow - Main benefit (1 min)
4. ⚫ Black  - Main risk (1 min)
5. 🎩 Blue   - Decide (1 min)

### For CREATIVE Sessions:
1. 🎩 Blue   - Set creative challenge
2. 💚 Green  - Generate ideas freely (bulk)
3. 💛 Yellow - Find value in each idea
4. ⚫ Black  - Identify issues to solve
5. 💚 Green  - Modify and improve
6. 🎩 Blue   - Select ideas to develop

示例

示例 1:评估新产品发布

背景: SaaS 公司正在考虑推出一款移动应用

🎩 蓝帽(设置):

我们正在评估是否为项目管理工具推出移动应用。我们要决定:开发、不开发,还是以后再开发。每顶帽子花 5 分钟。

⬜ 白帽(事实):

  • 34% 的用户通过移动浏览器访问
  • 竞争对手 X 和 Y 都有应用(评分分别为 4.2 和 3.8 星)
  • 开发预估:4-6 个月,$120K
  • 我们的 NPS 为 47(桌面用户)
  • 移动浏览器跳出率:67%(桌面端为 23%)
  • 我们有 2 名可用的移动开发人员

❤️ 红帽(感受):

  • “很兴奋——这可能会带来新的使用场景”
  • “担心这笔投入”
  • “遗憾我们没早点做”
  • “直觉告诉我,用户想要这个”

💛 黄帽(益处):

  • 降低移动用户的使用阻力(67% 的跳出率 → 有望获益)
  • 与 X 和 Y 达到竞争同等水平
  • 推送通知 = 更高的参与度
  • 将产品定位为“随时随地工作”工具
  • 如果 20% 的移动端跳出用户转化,每月可新增 400 名用户

⚫ 黑帽(风险):

  • 6 个月的开发时间 = 机会成本(我们还能开发什么?)
  • 移动应用需要持续维护(占开发时间的 15-20%)
  • 应用商店评论是公开的——发布不顺可能损害声誉
  • 我们的移动开发人员从未发布过应用
  • 桌面端功能请求不断积压

💚 绿帽(替代方案):

  • 使用渐进式 Web 应用(PWA),而不是原生应用?
  • 与应用开发机构合作?
  • 仅包含 3 项核心功能来发布 MVP?
  • 先为一个平台开发(iOS 或 Android)?
  • 收购一家已有应用的小型竞争对手?

🎩 蓝帽(结论):

决策:先开发 PWA(风险较低、速度较快)。如果 3 个月内每周用户数超过 1,000 人,就批准原生应用开发。


示例 2:快速定价决策

背景: 我们是否应该涨价 20%?

⬜ 白帽(30 秒): 当前价格为 $99。竞争对手的价格在 $79-$149 之间。上次涨价是在 18 个月前。月流失率为 4.2%。

❤️ 红帽(30 秒):“担心客户会强烈反对。”“不过感觉早就该涨了。”

💛 黄帽(30 秒): 现有客户带来的收入增加 20%。将我们定位为高端品牌。为产品改进提供资金。

⚫ 黑帽(30 秒): 部分客户会流失。获客可能会受到影响。经济前景不确定,时机不佳。

🎩 蓝帽(30 秒): 决策:仅对新客户涨价 15%。现有客户 6 个月内维持原价。之后重新评估。


检查清单与模板

六顶思考帽分析模板
## Six Thinking Hats Analysis

**Subject:** [What are we analyzing?]
**Date:** [Date]
**Participants:** [Who's involved?]

---

### 🎩 BLUE HAT - Setup
**Problem/Question:**
**Desired Outcome:**
**Time per Hat:**

---

### ⬜ WHITE HAT - Facts
**What we know:**
-
-
-

**What we don't know:**
-
-

**Data sources:**
-

---

### ❤️ RED HAT - Feelings
**Positive feelings:**
-

**Concerns/negative feelings:**
-

**Gut instinct:**
-

---

### 💛 YELLOW HAT - Benefits
**Key benefits:**
-
-
-

**Best-case scenario:**
-

**Who gains and how:**
-

---

### ⚫ BLACK HAT - Risks
**Key risks:**
-
-
-

**What could go wrong:**
-

**Obstacles:**
-

---

### 💚 GREEN HAT - Alternatives
**Alternative approaches:**
-
-
-

**Modifications to improve:**
-

**Wild ideas:**
-

---

### 🎩 BLUE HAT - Conclusion
**Summary of insights:**


**Decision:**


**Next steps:**
1.
2.
3.

会议引导指南
## Running a Six Hats Meeting

### Preparation
- [ ] Define the topic/decision clearly
- [ ] Prepare White Hat data in advance
- [ ] Allocate time per hat (typically 5-10 min each)
- [ ] Brief participants on the method

### Rules to Establish
1. Everyone wears the same hat at the same time
2. No criticism during Green Hat
3. Red Hat feelings need no justification
4. Black Hat must be specific, not vague
5. Blue Hat facilitator controls hat switches

### Facilitation Tips
- Use physical props (colored cards/hats) if in person
- Announce hat switches clearly
- Redirect off-hat comments ("Let's save that for Black Hat")
- Keep time visible
- Capture outputs for each hat
- End with clear next steps

### Common Pitfalls
- Skipping Red Hat (emotions surface anyway, better explicit)
- Too much time on Black Hat (negativity spiral)
- Not enough time on Green Hat (settling for obvious)
- Mixing hats (debating during White Hat)

技能边界

此技能擅长的方面
  • 构建有说服力的内容
  • 运用文案框架
  • 创建不同版本的草稿
  • 分析竞争对手的做法
此技能无法做到的方面
  • 保证转化率
  • 取代品牌声音的塑造
  • 了解你的特定受众
  • 作出最终审批决定

参考资料

  • de Bono, Edward.《Six Thinking Hats》(1985)
  • de Bono, Edward.《Lateral Thinking》(1967)
  • de Bono Group - 官方培训材料
  • Harvard Business Review - “Six Thinking Hats” 应用研究

相关技能


技能元数据(内部使用)

name: six-thinking-hats
category: strategy
subcategory: decision-making
version: 1.0
author: MKTG Skills
source_expert: Edward de Bono
source_work: Six Thinking Hats (1985)
difficulty: beginner
estimated_value: $500 workshop
tags: [decision-making, creativity, meetings, problem-solving, de Bono]
created: 2025-01-25
updated: 2025-01-25

评论

支持 Markdown