Six Thinking Hats parallel thinking—explore from six perspectives (facts, feelings, caution, benefits, creativity, process). Use for group decisions or ensuring all angles are considered.
npx skills add https://github.com/neurofoo/agent-skills --skill sixhats
Explore a topic from all six perspectives—facts, feelings, caution, benefits, creativity, and process.
Work through each hat sequentially, giving full attention to one perspective before moving to the next. This is parallel thinking, not debate.
Topic: [What we're exploring]
*What do we know? What data do we have?*
Known Facts
Information Gaps
*How do we feel about this? What does gut instinct say?*
Emotional Reactions
Intuitions
No justification needed—this hat is about feelings, not reasons.
*What could go wrong? What are the risks and problems?*
Risks
| Risk | Likelihood | Severity |
|------|------------|----------|
| [risk] | High/Med/Low | High/Med/Low |
Why It Might Fail
*What's good about this? What value does it offer?*
Benefits
| Benefit | Who Benefits | Magnitude |
|---------|--------------|-----------|
| [benefit] | [stakeholder] | High/Med/Low |
Best Case Scenario
If everything goes well: [description]
*What else is possible? What new ideas emerge?*
Alternative Approaches
Wild Ideas (don't filter)
*What have we learned? What should we do next?*
Summary of Perspectives
| Hat | Key Insight |
|-----|-------------|
| White | [main data point] |
| Red | [main feeling] |
| Black | [main concern] |
| Yellow | [main benefit] |
| Green | [best alternative] |
Recommended Next Steps
Decision/Direction
Based on all six perspectives:
> [Recommendation or decision]
$ARGUMENTS
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take neurofoo/sixhats from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.