Skip to content
Back to skills

Six Thinking Hats

ASecurity

Analyze decisions using six perspectives with structured parallel thinking.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 11, 2026
documentationgoreact

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned November 11, 2026

npx -y skills add johnalbertini14-glitch/openclaw-skills --skill six-thinking-hats --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Six Thinking Hats?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Six Thinking Hats
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/johnalbertini14-glitch-six-thinking-hats/badge)](https://www.skillsdirectory.com/skills/johnalbertini14-glitch-six-thinking-hats)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: Six Thinking Hats
slug: six-thinking-hats
version: 1.0.0
homepage: https://clawic.com/skills/six-thinking-hats
description: Analyze decisions using six perspectives with structured parallel thinking.
metadata: {"clawdbot":{"emoji":"🎩","requires":{"bins":[]},"os":["linux","darwin","win32"]}}
---

## Setup

If `~/six-thinking-hats/` doesn't exist, or memory shows setup incomplete, read `setup.md` first.

## When to Use

User needs to analyze a decision, problem, or idea thoroughly. Agent applies De Bono's Six Thinking Hats method to explore all angles systematically.

## Architecture

Memory lives in `~/six-thinking-hats/`. See `memory-template.md` for structure.

```
~/six-thinking-hats/
β”œβ”€β”€ memory.md       # Preferences + past analyses
└── archive/        # Completed analyses
```

## Quick Reference

| Topic | File |
|-------|------|
| Setup process | `setup.md` |
| Memory template | `memory-template.md` |
| Hat details | `hats.md` |

## The Six Hats

| Hat | Focus | Key Question |
|-----|-------|--------------|
| White | Facts, data | What do we know? What data is missing? |
| Red | Emotions, intuition | How do I feel about this? Gut reaction? |
| Black | Risks, problems | What could go wrong? Why might this fail? |
| Yellow | Benefits, value | What are the advantages? Best case? |
| Green | Creativity, alternatives | What else is possible? New ideas? |
| Blue | Process, control | What's the next step? Summary? |

## Core Rules

### 1. One Hat at a Time
- Wear only ONE hat at each moment
- Complete that perspective before switching
- Announce hat changes explicitly

### 2. Sequence Matters
Standard sequence for decisions:
1. **Blue** β€” Define the problem
2. **White** β€” Gather facts
3. **Green** β€” Generate options
4. **Yellow** β€” Evaluate benefits (per option)
5. **Black** β€” Evaluate risks (per option)
6. **Red** β€” Gut check
7. **Blue** β€” Conclude and decide

### 3. Keep It Parallel
- Everyone thinks in the same direction
- No arguing or defending
- Each hat gets its full moment

### 4. Red Hat Is Brief
- Emotions only, no justification
- 30 seconds max
- "I feel excited" not "I feel excited because..."

### 5. Black Hat Is Not Negative
- Critical thinking, not negativity
- Identifies risks to ADDRESS, not to reject
- Paired with Yellow for balance

### 6. Green Hat Forces Output
- Generate at least 3 alternatives
- No judgment during Green
- Quantity over quality first

### 7. Blue Hat Owns the Process
- Opens and closes the session
- Summarizes each hat's findings
- Makes the meta-decisions

## Output Format

When analyzing a decision, structure output as:

```markdown
## Analysis: [Topic]

### Blue Hat: Framing
[Problem statement, scope, goal]

### White Hat: Facts
[Known data, missing information, sources]

### Green Hat: Options
1. [Option A]
2. [Option B]
3. [Option C]

### Yellow Hat: Benefits
| Option | Benefits |
|--------|----------|
| A | [benefits] |
| B | [benefits] |
| C | [benefits] |

### Black Hat: Risks
| Option | Risks |
|--------|-------|
| A | [risks] |
| B | [risks] |
| C | [risks] |

### Red Hat: Gut Check
[Brief emotional response to each option]

### Blue Hat: Conclusion
[Summary, recommendation, next steps]
```

## Common Traps

- Mixing hats β†’ analysis becomes confused, key perspectives missed
- Skipping Red β†’ ignoring intuition that might catch what logic misses
- Black without Yellow β†’ decisions feel negative, good options get rejected
- Green without constraints β†’ impractical ideas waste time
- No Blue at end β†’ analysis without actionable conclusion

## Related Skills
Install with `clawhub install <slug>` if user confirms:
- `decide` β€” decision frameworks
- `brainstorm` β€” creative idea generation
- `first-principles-thinking` β€” foundational analysis

## Feedback

- If useful: `clawhub star six-thinking-hats`
- Stay updated: `clawhub sync`

Files in this skill

  • SKILL.md3.8 KB
  • _meta.json291 B
  • hats.md3.3 KB
  • memory-template.md957 B
  • setup.md1.5 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in documentation β†’

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.