Skills

Six Thinking Hats

Apply Edward de Bono's Six Thinking Hats methodology to software testing for...

Install

npx skills add proffesor-for-testing/agentic-qe --skill six-thinking-hats -g -a claude-code -y
Category
Design
Updated
3d ago
License
MIT
Context cost
Mediumabout 1,685 tokens
Runs scripts
No, instructions only

What it does

Apply Edward de Bono's Six Thinking Hats methodology to software testing for comprehensive quality analysis. Use when designing test strategies, conducting test retrospectives, analyzing test failures, evaluating testing approaches, or facilitating testing discussions. Each hat provides a distinct testing perspective: facts (White), risks (Black), benefits (Yellow), creativity (Green), emotions (Red), and process (Blue).

Six Thinking Hats for Testing

<default_to_action> When analyzing testing decisions:

  1. DEFINE focus clearly (specific testing question)
  2. APPLY each hat sequentially (5 min each)
  3. DOCUMENT insights per hat
  4. SYNTHESIZE into action plan

Quick Hat Rotation (30 min):

šŸ¤ WHITE (5 min) - Facts only: metrics, data, coverage
ā¤ļø RED (3 min) - Gut feelings (no justification needed)
šŸ–¤ BLACK (7 min) - Risks, gaps, what could go wrong
šŸ’› YELLOW (5 min) - Strengths, opportunities, what works
šŸ’š GREEN (7 min) - Creative ideas, alternatives
šŸ”µ BLUE (3 min) - Action plan, next steps

Example for "API Test Strategy":

  • šŸ¤ 47 endpoints, 30% coverage, 12 integration tests
  • ā¤ļø Anxious about security, confident on happy paths
  • šŸ–¤ No auth tests, rate limiting untested, edge cases missing
  • šŸ’› Good docs, CI/CD integrated, team experienced
  • šŸ’š Contract testing with Pact, chaos testing, property-based
  • šŸ”µ Security tests first, contract testing next sprint </default_to_action>

Quick Reference Card

The Six Hats

HatFocusKey Question
šŸ¤ WhiteFacts & DataWhat do we KNOW?
ā¤ļø RedEmotionsWhat do we FEEL?
šŸ–¤ BlackRisksWhat could go WRONG?
šŸ’› YellowBenefitsWhat's GOOD?
šŸ’š GreenCreativityWhat ELSE could we try?
šŸ”µ BlueProcessWhat should we DO?

When to Use Each Hat

HatUse For
šŸ¤ WhiteBaseline metrics, test data inventory
ā¤ļø RedTeam confidence check, quality gut feel
šŸ–¤ BlackRisk assessment, gap analysis, pre-mortems
šŸ’› YellowStrengths audit, quick win identification
šŸ’š GreenTest innovation, new approaches, brainstorming
šŸ”µ BlueStrategy planning, retrospectives, decision-making

Hat Details

šŸ¤ White Hat - Facts & Data

Output: Quantitative testing baseline

Read the whole SKILL.md on GitHub

More in Design