Getting Claude to Adversarially Debate Without Caving: 5 Prompt Tweaks That Work

The developer behind Spar (sparwithai.com) shared what worked to get Claude to argue against users across 5 escalating rounds without defaulting to agreement. The core problem: Claude's default is to find common ground, hedge, and validate. Here are the five prompting moves that fixed it.
1. Define the Role as a Position, Not a Persona
Early prompts like "you are a skilled debater" gave Claude a character but didn't constrain behavior. The fix was explicit negative constraints: cannot concede, cannot soften, cannot find middle ground, cannot say "you raise a good point". Negative constraints turned out more important than positive ones.
2. Treat Each Round as Having a Different Objective
Instead of one prompt for the whole debate, each round gets its own goal:
- Round 1: Identify the weakest premise.
- Round 2: Attack evidence quality.
- Round 3: Find internal contradictions.
- Round 4: Push the position to its uncomfortable logical extreme.
- Round 5: Reframe through a perspective the user hasn't considered.
This stopped the conversation from collapsing into generic counterarguments.
3. Force Engagement with the User's Specific Words
Without this, Claude argues against a generic version of the position. The developer added explicit instructions to quote the user's reasoning back and attack that — not a steelman or strawman. This was the single biggest quality jump.
4. Explicitly Ban Sycophancy and Fabrication
Even with adversarial framing, Claude slips into "that's a thoughtful point, however..." or invents statistics. The prompt now explicitly bans: do not create false narratives, do not invent sources or statistics, do not flatter before disagreeing, do not concede ground that wasn't conceded. Calling out fabrication by name cut it down significantly.
5. Let It Be Uncomfortable
Every safety reflex wants to add "respectfully" and "with empathy." The developer explicitly instructed that the user opted in to being challenged, and softening the argument is failing the user, not protecting them.
Next Steps
The developer is focusing on: better handling of subjective positions, stronger engagement with longer inputs, and more variety in counterargument patterns for commonly debated topics.
Full discussion and link to try it: sparwithai.com
📖 Read the full source: r/ClaudeAI
👀 See Also

Run Claude Code in VSCode/Cursor Integrated Terminal for Better Workflow
Running Claude Code in the VSCode or Cursor integrated terminal instead of an external terminal provides immediate access to git diff panels and debuggers without switching windows, with no configuration required.

Don't Just Paste the AI — Write Your Own Take
A direct plea to developers: stop copying AI chatbot answers verbatim. Use AI as a drafting partner, then rewrite the reply in your own words.

A Two-Step AI Workflow for Legacy Code Modernization
A Reddit post outlines a two-step 'reverse engineering' approach for using AI with legacy code: first extract business logic into a technology-agnostic Business Requirement Document, then use a 'Master Architect' prompt to rebuild from scratch with modern best practices.

Why Your OpenClaw Scheduled/Cronjob Tasks Fail
When you ask an agent to create a scheduled task, it often creates a shell or Python script instead of using OpenClaw's prompt-in-cron feature. This makes tasks non-agentic and inefficient.