six-thinking-hats

The Six Thinking Hats for Testing skill provides a structured framework for software quality engineering, enabling teams and agents to explore testing challenges from six distinct psychological perspectives. By decomposing complex testing problems into these specific domains—facts (White), risks (Black), benefits (Yellow), creativity (Green), emotions (Red), and process (Blue)—the agent ensures that no aspect of a testing strategy is overlooked, preventing tunnel vision and bias during critical decision-making sessions.

This skill is designed for QE engineers, architects, and AI-driven autonomous agents who need to perform test retrospectives, conduct risk assessments, design regression strategies, or facilitate testing discussions. It replaces ad-hoc brainstorming with a proven parallel thinking technique, allowing for rigorous coverage of both technical metrics and human-centric feedback. It integrates seamlessly with other quality tools in the agentic-qe repository, including test generators and security scanners.

• Sequential Thinking: Forces a systematic workflow from data gathering (White Hat) to emotional check-ins (Red Hat) and finally concrete process planning (Blue Hat).

• Comprehensive Perspective: Identifies coverage gaps (Black Hat) while surfacing potential quick wins and automation opportunities (Yellow Hat).

• Creative Innovation: Encourages unconventional testing methods like property-based testing, chaos engineering, and AI-powered test generation (Green Hat).

• Collaborative Alignment: Standardizes how teams communicate quality concerns, reducing ambiguity and conflict in test planning.

• Integration Capability: Easily integrates with fleet management systems to trigger parallel execution by specialized agents (e.g., qe-quality-analyzer, qe-regression-risk-analyzer).

• Action-Oriented Outcomes: Ensures every session concludes with a clear, prioritized action plan with assigned responsibilities.

• When invoking this skill, provide a specific topic or testing question (e.g., 'API Test Strategy', 'Authentication Module Review') to focus the analysis.

• The skill assumes a 30-minute default session duration but can be adjusted for team-based meetings of 60 minutes or longer.

• Expected inputs include codebase context, current test metrics, and architectural diagrams to maximize the relevance of the White Hat findings.

• Typical outputs are structured markdown reports detailing findings for each hat, culminating in a prioritized task list for the next sprint or development cycle.

• Useful for navigating complex CI/CD pipeline challenges, security audits, and post-incident retrospectives.