six-thinking-hats

Apply Six Thinking Hats to software testing decisions and generate structured outputs.

436|78|Updated Sep 11, 2025
One-click install
npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill six-thinking-hats
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: six-thinking-hats
Source: https://github.com/proffesor-for-testing/agentic-qe/tree/main/.claude/skills/six-thinking-hats
Command: npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill six-thinking-hats

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill applies Edward de Bono's Six Thinking Hats to software testing, enabling structured, multi-perspective analysis to uncover blind spots and improve decisions.

Core Features & Use Cases

  • Hats for Testing: White (facts), Red (feelings), Black (risks), Yellow (benefits), Green (creativity), Blue (process).
  • Team Collaboration: Facilitates faster, more aligned testing discussions.
  • Contextual Templates: Ready-to-use templates for solo or team sessions.

Quick Start

Run a 30-minute Six Hats session to generate a structured testing plan for a feature.

Frequently Asked Questions about six-thinking-hats

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How can I improve decision-making in software testing with structured perspectives?

The Six Thinking Hats methodology applies six distinct perspectives—facts, feelings, risks, benefits, creativity, and process—to testing decisions. Each hat focuses on a specific angle, helping teams uncover blind spots and reach aligned decisions faster than traditional brainstorming, whether in solo, team, or async sessions.

Can I use Six Thinking Hats for test strategy design and failure analysis?

Yes. Six Thinking Hats works for test strategy design, retrospectives, failure analyses, and evaluation of testing approaches. Each hat generates time-boxed, hat-specific outputs—white hat captures facts, red hat surfaces feelings, black hat identifies risks, yellow hat explores benefits, green hat drives ideas, and blue hat synthesizes action.

How do I run a structured testing discussion with my team in 30 minutes?

Use the ready-to-use templates for team sessions. Assign each hat role, work through each perspective in sequence, and generate machine-readable artifacts. The blue hat synthesizes findings into an action-oriented plan, turning multi-perspective analysis into concrete next steps for your testing approach.

What's the difference between Six Hats and traditional testing retrospectives?

Six Hats applies a formal, role-based structure that ensures each perspective—facts, risks, benefits, emotions, creativity, and process—gets dedicated time. This prevents dominant voices from drowning out viewpoints and produces time-boxed outputs suitable for agent integration and template-based workflows instead of open-ended discussion.

Do I need prior experience with collaborative frameworks to use this approach?

No. The Skill provides contextual templates and hat-specific prompts that guide both solo and team sessions. Each hat has a clear mandate—facts, feelings, risks, benefits, ideas, process—so participants can contribute meaningfully without prior framework experience.