nietzsche

Challenge plans and assumptions with adversarial critique per turn.

4|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/satsilem/claude-skills-pantheon --skill nietzsche
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nietzsche
Source: https://github.com/satsilem/claude-skills-pantheon/tree/main/skills/nietzsche
Command: npx skills add https://github.com/satsilem/claude-skills-pantheon --skill nietzsche

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adversarial thinking partner that challenges your ideas, plans, and decisions before you commit to them. Default mode is constructive disagreement, not validation. Use when you want pushback, devil's advocate analysis, or stress-testing of a position. Triggers on: "Nietzsche", "challenge this", "poke holes in this", "play devil's advocate", "stress-test my plan", "argue against this", "I want pushback", "what am I missing", or whenever the user shares a decision/plan and explicitly wants opposition rather than agreement. Do not invoke for routine help requests where the user wants collaboration, not confrontation.

Core Features & Use Cases

  • Stress-testing decisions before committing
  • Identifying weak points in plans, proposals, or arguments
  • Surfacing assumptions the user has not examined
  • Reviewing work where the user wants the weakest points called out first

Quick Start

Ask Nietzsche to challenge your plan by stating the strongest counter-argument and the untested assumption behind it.

Frequently Asked Questions about nietzsche

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

FAQPage Schema
How do I stress-test my business plan before committing to it?

You can surface untested assumptions by requesting devil's advocate analysis, which challenges your core arguments and delivers targeted critiques to expose blind spots in your technical or business decisions.

What is the best way to get pushback on a technical design decision?

This approach works across technical, business, and design contexts by providing a single, targeted critique per turn, but it requires explicit user prompts to initiate pushback and does not suit routine collaborative help requests.

How do I identify weak points in a project proposal using devil's advocate analysis?

You trigger pushback by using explicit phrases like "challenge this," "poke holes in this," or "what am I missing," ensuring the system understands you want opposition rather than validation for your plan.

When should I not use adversarial critique for reviewing my plans?

You should not use adversarial critique for routine help requests where you want collaboration and validation, as this approach defaults to constructive disagreement and confrontation rather than supportive agreement.