challenge-that

Analyze proposals from five adversarial perspectives to surface assumptions and tradeoffs.

334|43|Updated Nov 14, 2025
One-click install
npx skills add https://github.com/NTCoding/claude-skillz --skill challenge-that
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: challenge-that
Source: https://github.com/NTCoding/claude-skillz/tree/main/challenge-that
Command: npx skills add https://github.com/NTCoding/claude-skillz --skill challenge-that

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Force critical evaluation of proposals by analyzing from multiple adversarial perspectives.

Core Features & Use Cases

  • Five-perspective critique: evaluates proposals from Skeptic, Pragmatist, Edge Case Hunter, Structural Critic, and Root Cause Analyst.
  • Actionable output: synthesizes concerns and recommended next steps.
  • Use Case: during requirements reviews and design decisions to surface hidden assumptions and tradeoffs.

Quick Start

Invoke /challenge-that on a proposal or decision to trigger adversarial critique. Review the generated challenges and decide which concerns to address before proceeding.

Frequently Asked Questions about challenge-that

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I critique a proposal from multiple adversarial perspectives?

To critique a proposal from multiple adversarial perspectives, you apply a five-perspective analysis framework covering Skeptic, Pragmatist, Edge Case Hunter, Structural Critic, and Root Cause Analyst. This forces explicit challenge of assumptions and surfaces tradeoffs.

What is the best way to surface hidden assumptions during requirements review?

The best way to surface hidden assumptions during requirements review is to trigger an adversarial critique on the proposal. This evaluates the requirements from five distinct perspectives to ensure explicit challenge and yield actionable concerns.

How do I get actionable concerns from a decision analysis?

You get actionable concerns from a decision analysis by rigorously evaluating the proposal through multiple adversarial perspectives. This process synthesizes concerns and recommended next steps, ensuring tradeoffs are surfaced before proceeding.

Can I use adversarial perspectives to evaluate design decisions across projects?

Yes, you can use adversarial perspectives to evaluate design decisions across projects. Applying a five-perspective critique to design decisions forces critical evaluation, surfaces hidden tradeoffs, and yields actionable concerns for your project.

When do I need to force critical evaluation of a proposal?

You need to force critical evaluation of a proposal during requirements reviews and design decisions. Applying multiple adversarial perspectives ensures explicit challenge of assumptions and yields actionable concerns before you proceed.