Force critical evaluation of any proposal, decision, or approach from 5 adversarial perspectives. Use when you've just agreed to something, accepted a plan, or want to stress-test an idea before committing. Triggers on: 'challenge this', 'stress test', 'devil's advocate', 'what could go wrong', 'poke holes', 'is this a good idea', 'evaluate this critically'.
Installs into .claude/skills of the current project.
Are you the author of Challenge That?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/onfire7777-challenge-that)
---
name: challenge-that
description: "Force critical evaluation of any proposal, decision, or approach from 5 adversarial perspectives. Use when you've just agreed to something, accepted a plan, or want to stress-test an idea before committing. Triggers on: 'challenge this', 'stress test', 'devil's advocate', 'what could go wrong', 'poke holes', 'is this a good idea', 'evaluate this critically'."
---
# Challenge That
Force critical evaluation by analyzing from multiple adversarial perspectives.
## When Invoked
1. Identify what was just accepted/proposed in this conversation
2. State it clearly: "**Challenging:** [the proposal/decision]"
3. Analyze from each of the five perspectives below
4. Synthesize into actionable concerns
5. Ask: "Which concerns should we address before proceeding?"
## The Five Hats
| Hat | Focus | Key Questions |
|-----|-------|---------------|
| π΄ **Skeptic** | Evidence & proof | "What evidence supports this? Has this been validated? Are we guessing?" |
| π‘ **Pragmatist** | Cost/benefit | "Is this the simplest fix? What's the maintenance burden? Is it worth it?" |
| π’ **Edge Case Hunter** | Failure modes | "What breaks this? What's the worst case? What did we miss?" |
| π΅ **Structural Critic** | Architecture | "Is this the right location? Does it fit the existing design? Will it cause problems elsewhere?" |
| π£ **Root Cause Analyst** | Problem diagnosis | "Is the problem correctly identified? Are we treating symptoms? What's the actual cause?" |
## Output Format
```
## Challenging: [proposal/decision being challenged]
### π΄ Skeptic
[Challenge from evidence/proof perspective]
### π‘ Pragmatist
[Challenge from cost/benefit perspective]
### π’ Edge Case Hunter
[Challenge from failure modes perspective]
### π΅ Structural Critic
[Challenge from architecture perspective]
### π£ Root Cause Analyst
[Challenge from problem diagnosis perspective]
---
**Key Concerns:**
1. [Most significant concern]
2. [Second concern]
3. [Third concern]
Which of these should we address before proceeding?
```
## Rules
π¨ **Be genuinely adversarial.** Don't softball the challenges. If a perspective finds nothing wrong, say soβbut look hard first.
π¨ **Challenge the proposal, not the person.** Focus on the idea's weaknesses, not who suggested it.
π¨ **Provide actionable output.** Each challenge should point to something that could be investigated or changed.