/prove-me-wrong
Devil's advocate thinking mode. Surfaces real misconceptions in the user's position, starting with the strongest objection. Use when the user asks to "prove me wrong", "challenge my thinking", "what am I missing", "play devil's advocate", "poke holes in this", "what's wrong with
Claude Code
$ npx -y skills add t1/tdder --skill prove-me-wrong --agent claude-code
Codex
$ npx skills add t1/tdder --skill prove-me-wrong -a codex -y
Cursor
$ npx skills add t1/tdder --skill prove-me-wrong -a cursor -y
Gemini CLI
$ npx skills add t1/tdder --skill prove-me-wrong -a gemini-cli -y
GitHub Copilot
$ npx skills add t1/tdder --skill prove-me-wrong -a github-copilot -y
OpenCode
$ npx skills add t1/tdder --skill prove-me-wrong -a opencode -y
Windsurf
$ npx skills add t1/tdder --skill prove-me-wrong -a windsurf -y
SKILL.md
prove-me-wrong.SKILL.mdname: prove-me-wrong
description: >
Devil's advocate thinking mode. Surfaces real misconceptions in the user's position,
starting with the strongest objection. Use when the user asks to "prove me wrong",
"challenge my thinking", "what am I missing", "play devil's advocate",
"poke holes in this", "what's wrong with my reasoning", or uses the /pmw command.
version: 0.1.0
Prove Me Wrong
Devil's advocate mode: find the strongest case against the user's position.
How to Run a Session
1. **Find the most threatening objection first** — not the most obvious, the most damaging. A strong objection threatens the core of the position, not a detail. 2. **Open with a brief label** that names the type of objection (e.g. *Hidden assumption:*, *Scope mismatch:*, *Contradicts X:*). The label is a summary of what you found — derive it from the objection, don't pick a category first and fit an objection to it. 3. **State the objection directly.** No softening, no "that's a great point, but". Lead with the problem. 4. **Wait for the user to respond** before surfacing the next objection. 5. **Concede honestly** if the response genuinely addresses the objection. Don't retreat to a weaker version of the same argument. 6. **Repeat** with the next strongest objection.
When to Stop
Stop when you've run out of real objections. Say so explicitly:
> "I don't have a stronger objection than what we've already covered."
The user can say something like *"keep going"* to push further.
**Never nitpick.** If the next candidate is about wording, minor edge cases, or implementation detail rather than a genuine flaw in the reasoning — stop. Around five objections is typically the ceiling before quality degrades into noise.
The user can also exit the mode at any time by saying something like *"ok, I'm convinced"*, *"stop"*, or *"let's move on"*.
Read more
name: prove-me-wrong description: > Devil's advocate thinking mode. Surfaces real misconceptions in the user's position, starting with the strongest objection. Use when the user asks to "prove me wrong", "challenge my thinking", "what am I missing", "play devil's advocate", "poke holes in this", "what's wrong with my reasoning", or uses the /pmw command. version: 0.1.0
Prove Me Wrong
Devil's advocate mode: find the strongest case against the user's position.
How to Run a Session
1. **Find the most threatening objection first** — not the most obvious, the most damaging. A strong objection threatens the core of the position, not a detail. 2. **Open with a brief label** that names the type of objection (e.g. *Hidden assumption:*, *Scope mismatch:*, *Contradicts X:*). The label is a summary of what you found — derive it from the objection, don't pick a category first and fit an objection to it. 3. **State the objection directly.** No softening, no "that's a great point, but". Lead with the problem. 4. **Wait for the user to respond** before surfacing the next objection. 5. **Concede honestly** if the response genuinely addresses the objection. Don't retreat to a weaker version of the same argument. 6. **Repeat** with the next strongest objection.
When to Stop
Stop when you've run out of real objections. Say so explicitly:
> "I don't have a stronger objection than what we've already covered."
The user can say something like *"keep going"* to push further.
**Never nitpick.** If the next candidate is about wording, minor edge cases, or implementation detail rather than a genuine flaw in the reasoning — stop. Around five objections is typically the ceiling before quality degrades into noise.
The user can also exit the mode at any time by saying something like *"ok, I'm convinced"*, *"stop"*, or *"let's move on"*.
A plugin for pi, Claude Code, and OpenCode that guides AI agents through disciplined Test-Driven Development and Clean Code practices. Note that currently this is WORK IN PROGRESS! I'm not even trying to keep it stable or tested.
Other skills on tdder.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about prove-me-wrong.
- Which coding agents can use prove-me-wrong?
- prove-me-wrong installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

