Index of every page on this site: llms.txt
All skills
ntcoding avatar

/challenge-that

@21c6101
by Nick Tunentcoding/claude-skillz366 stars
47
Run it yourself

Force critical evaluation of proposals, requirements, or decisions by analyzing from multiple adversarial perspectives. Triggers on: accepting a proposal without pushback, 'sounds good', 'let's go with', design decisions with unstated tradeoffs, unchallenged assumptions, premature consensus. Invoke with /challenge-that.

Use this Skill: https://skilld.dev/gh/ntcoding/claude-skillz/challenge-that

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈84 tokens for metadata: the name and description. ≈1k when used: this file. ≈534 more on demand in 1 file.

Description uses 4.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈338 characters, or 4.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Challenge That

Force critical evaluation by analyzing from multiple adversarial perspectives.

When to Use

Invoke /challenge-that when:

  • Claude accepted a proposal without critical evaluation
  • You want to stress-test a decision before committing
  • Requirements feel under-examined
  • Something seems off but you can't articulate why

The Five Hats

Each perspective challenges from a different angle:

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?"

Behavior

When /challenge-that is invoked:

  1. Identify what was just accepted/proposed
  2. State it clearly: "Challenging: [the proposal/decision]"
  3. Analyze from each of the five perspectives
  4. Synthesize into actionable concerns
  5. Ask: "Which concerns should we address before proceeding?"

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?

Critical 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.

Example

User: /challenge-that

Context: Claude just accepted a proposal to add edge case validation to TDD's GREEN state.

Output:

Challenging: Add edge case validation checklist to TDD GREEN state

🔴 Skeptic

What evidence shows that GREEN state is the right location? The proposal assumes this will catch bugs, but has anyone tested whether developers actually use checklists at this stage? GREEN means "tests pass"—adding a review step here changes what GREEN means.

🟡 Pragmatist

This adds friction to every TDD cycle. Is the bug frequency high enough to justify the overhead? The PR mentioned 3 bugs in one PR—is that representative or an outlier? What's the cost of false negatives (checklist fatigue)?

🟢 Edge Case Hunter

What happens when the checklist reveals missing tests? There's no GREEN → PLANNING transition. The developer would need to either ignore the finding or break the state machine. This creates a dead end.

🔵 Structural Critic

GREEN state is about code quality assessment, not test coverage. Test writing happens in PLANNING. This checklist belongs in PLANNING state where tests are actually written—not after they've already passed.

🟣 Root Cause Analyst

The actual problem was insufficient edge case consideration during test writing. The proposal treats the symptom (bugs shipped) not the cause (incomplete test planning). Moving this to PLANNING would address the root cause.


Key Concerns:

  1. GREEN is structurally the wrong location—no recovery path exists
  2. Root cause is in PLANNING, not GREEN
  3. No evidence this will be used effectively at GREEN stage

Which of these should we address before proceeding?

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning1mo4 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    This skill is a critical-thinking framework that instructs the AI agent to evaluate proposals from multiple adversarial perspectives. It is entirely text-based and contains no executable code, external dependencies, or network operations.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

  • Runlayer9mo

    2/2 files flagged

Signed by skilld at 21c6101. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Dormantupdated 10 months ago
version
1.0.0

README badge

README badge for ntcoding/claude-skillz/challenge-that