proffesor-for-testing/agentic-qe/six-thinking-hats
Claude Code and agent skill by proffesor-for-testing/agentic-qe
- community
Checking that the SKILL.md file is still in the repository.
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).
Install
npx vskill@latest install proffesor-for-testing/agentic-qe/six-thinking-hatsSKILL.md
Six Thinking Hats for Testing
<default_to_action> When analyzing testing decisions:
- DEFINE focus clearly (specific testing question)
- APPLY each hat sequentially (5 min each)
- DOCUMENT insights per hat
- SYNTHESIZE into action plan
Quick Hat Rotation (30 min):
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
| Hat | Focus | Key Question | |
|---|---|---|---|
| π€ White | Facts & Data | What do we KNOW? | |
| β€οΈ Red | Emotions | What do we FEEL? | |
| π€ Black | Risks | What could go WRONG? | |
| π Yellow | Benefits | What's GOOD? | |
| π Green | Creativity | What ELSE could we try? | |
| π΅ Blue | Process | What should we DO? |
When to Use Each Hat
| Hat | Use For | |
|---|---|---|
| π€ White | Baseline metrics, test data inventory | |
| β€οΈ Red | Team confidence check, quality gut feel | |
| π€ Black | Risk assessment, gap analysis, pre-mortems | |
| π Yellow | Strengths audit, quick win identification | |
| π Green | Test innovation, new approaches, brainstorming | |
| π΅ Blue | Strategy planning, retrospectives, decision-making |
Hat Details
π€ White Hat - Facts & Data
Output: Quantitative testing baseline
Questions:
- What test coverage do we have?
- What is our pass/fail rate?
- What environments exist?
- What is our defect history?
π€ Black Hat - Risks & Cautions
Output: Comprehensive risk assessment
Questions:
- What could go wrong in production?
- What are we NOT testing?
- What assumptions might be wrong?
- Where are the coverage gaps?
π Yellow Hat - Benefits & Optimism
Output: Strengths and opportunities
Questions:
- What's working well?
- What strengths can we leverage?
- What quick wins are available?
π Green Hat - Creativity
Output: Innovative testing ideas
Questions:
- How else could we test this?
- What if we tried something completely different?
- What emerging techniques could we adopt?
β€οΈ Red Hat - Emotions
Output: Team gut feelings (NO justification needed)
Questions:
- How confident do you feel about quality?
- What makes you anxious?
- What gives you confidence?
π΅ Blue Hat - Process
Output: Action plan with owners and timelines
Questions:
- What's our strategy?
- How should we prioritize?
- What's the next step?
Session Templates
Solo Session (30 min)
Team Session (60 min)
- Each hat: 10 minutes
- Rotate through hats as group
- Document on shared whiteboard
- Blue Hat synthesizes at end
Agent Integration
Agent Coordination Hints
Memory Namespace
Fleet Coordination
Related Skills
- risk-based-testing - Black Hat deep dive
- exploratory-testing-advanced - Green Hat exploration
- context-driven-testing - Adapt to context
Anti-Patterns
| β Avoid | Why | β Instead | |
|---|---|---|---|
| Mixing hats | Confuses thinking | One hat at a time | |
| Justifying Red Hat | Kills intuition | State feelings only | |
| Skipping hats | Misses insights | Use all six | |
| Rushing | Shallow analysis | 5 min minimum per hat |
Remember
Separate thinking modes for clarity. Each hat reveals different insights. Red Hat intuition often catches what Black Hat analysis misses.
Everyone wears all hats. This is parallel thinking, not role-based. The goal is comprehensive analysis, not debate.
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingassets/skills/six-thinking-hats/SKILL.md
Popularity
- Repository stars
- 436
- Repository forks
- 78
- Repository npm downloads, 7 days
- 9,963
- 7-day trend score
- 51
Stars and forks are for the whole GitHub repository, not this skill alone. Downloads are for the repository's npm package. Refreshed 10 Aug 2026, 2 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/proffesor-for-testing/agentic-qe/six-thinking-hats)