Skill: ivangdavila/six-thinking-hats (version 1.0.0)

--- 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`

path: hats.md
content: # Hats Deep Dive — Six Thinking Hats

## White Hat: Facts and Information

**Focus:** Objective data only
**Mode:** Neutral, factual

### Questions to Ask
- What information do we have?
- What information is missing?
- How reliable is our data?
- What would we need to know?

### Output Style
- Bullet points of facts
- Clear "known" vs "unknown" sections
- Sources where applicable
- No interpretation or opinion

### Common Mistakes
- Including opinions disguised as facts
- Ignoring inconvenient data
- Not identifying what's missing

---

## Red Hat: Emotions and Intuition

**Focus:** Feelings, hunches, gut reactions
**Mode:** Personal, intuitive

### Questions to Ask
- How do I feel about this?
- What's my gut saying?
- What's my immediate reaction?
- Any hunches I can't explain?

### Output Style
- Brief, direct statements
- "I feel..." not "I think because..."
- No justification required
- 30 seconds max

### Common Mistakes
- Trying to justify feelings
- Dismissing intuition as irrational
- Spending too long analyzing emotions

---

## Black Hat: Caution and Risks

**Focus:** Critical thinking, what could go wrong
**Mode:** Cautious but constructive

### Questions to Ask
- What could go wrong?
- What are the risks?
- What obstacles exist?
- Why might this fail?

### Output Style
- List of specific risks
- Likelihood and impact where possible
- Factual concerns, not negativity
- Paired with potential mitigations

### Common Mistakes
- Being negative instead of critical
- Using it to kill ideas instead of improve them
- Not pairing with Yellow hat

---

## Yellow Hat: Benefits and Value

**Focus:** Optimism, advantages, best case
**Mode:** Positive, constructive

### Questions to Ask
- What are the benefits?
- What value does this create?
- What's the best case scenario?
- Why might this work?

### Output Style
- List of advantages
- Value propositions
- Positive outcomes
- Reasons for optimism

### Common Mistakes
- Unrealistic optimism
- Ignoring obvious problems
- Not being specific about benefits

---

## Green Hat: Creativity and Alternatives

**Focus:** New ideas, possibilities, alternatives
**Mode:** Creative, generative

### Questions to Ask
- What else is possible?
- What alternatives exist?
- How might we do this differently?
- What if we tried...?

### Output Style
- Multiple options (minimum 3)
- No judgment yet
- Build on others' ideas
- Quantity first, quality later

### Common Mistakes
- Judging ideas too early
- Settling for first idea
- Not pushing past obvious options

---

## Blue Hat: Process and Control

**Focus:** Managing the thinking process
**Mode:** Meta, organizational

### Questions to Ask
- What's our goal here?
- Which hat should we use next?
- What have we learned so far?
- What's the conclusion?

### Output Style
- Clear summaries
- Process decisions
- Next steps
- Final recommendations

### Common Mistakes
- Skipping the summary
- Not defining the problem clearly
- Forgetting to conclude

---

## Alternative Sequences

### For New Ideas
1. Blue (frame)
2. Green (generate)
3. Yellow (find value)
4. Black (find risks)
5. White (check facts)
6. Blue (decide)

### For Problem Solving
1. Blue (define problem)
2. White (gather data)
3. Black (identify causes)
4. Green (solutions)
5. Yellow (evaluate)
6. Blue (conclude)

### For Quick Decisions
1. Blue (frame)
2. White + Yellow + Black (rapid assessment)
3. Red (gut check)
4. Blue (decide)


path: memory-template.md
content: # Memory Template — Six Thinking Hats

Create `~/six-thinking-hats/memory.md` with this structure:

```markdown
# Six Thinking Hats Memory

## Status
setup: ongoing
version: 1.0.0
last_interaction: YYYY-MM-DD

## Preferences
output_format: full | abbreviated
archive_analyses: yes | no
favorite_sequence: standard | custom
emphasis_hats: [list of hats to spend more time on]

## Custom Sequences
<!-- If user prefers different hat orders for different contexts -->

## Recent Analyses
<!-- Last 3-5 analyses with dates and outcomes -->

---
*Updated: YYYY-MM-DD*
```

## Status Values

| Value | Meaning |
|-------|---------|
| `ongoing` | Still gathering preferences |
| `complete` | Fully configured |
| `paused` | User said "not now" |
| `never_ask` | User said stop asking |

## Notes

- Save incrementally — capture preferences as they emerge
- Archive completed analyses if user wants history
- Track which sequences work best for their decisions


path: setup.md
content: # Setup — Six Thinking Hats

## Your Mission

Make this skill **maximally useful** for THIS user's decision-making style.

## When to Read This

- `~/six-thinking-hats/` doesn't exist (first time)
- `memory.md` has `setup: ongoing` or `setup: paused`
- `memory.md` version < current skill version

## Before Anything

1. **Understand this skill completely** — read all files
2. **Analyze this user** — their decision style, typical problems
3. **Anticipate their day-to-day** — quick decisions vs deep analysis?

## Engage Thoughtfully

**Not blocking.** If user asks to analyze something, start analyzing. Gather preferences naturally.

**Adapt to user type:**
- Analytical: full structured output, all hats detailed
- Quick: abbreviated format, focus on key hats
- Creative: extra time on Green hat

**Save incrementally.** Every preference shared → save immediately.

### Key Questions

- Do they prefer full analysis or quick summaries?
- Which hats matter most in their context? (business → Black/Yellow, creative → Green/Red)
- Do they want archived analyses?
- Preferred output format?

### Show Value Immediately

As they share a decision to analyze, demonstrate the method working. They should feel the clarity of structured thinking immediately.

## On Version Updates

If skill version > memory.md version:
1. Check what's new
2. Propose relevant changes
3. Update version after changes applied

## Remember

Users don't want theory — they want better decisions. Show them the hats in action, not in explanation.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)