抬杠高手团队

Overview

The devil’s advocate role has a long history: one argues against a proposition not out of conviction, but to test whether the proposition can survive scrutiny. The Devil’s Advocate Team automates that discipline for individuals and groups who want intellectual exercise — stronger reasoning, fewer blind spots, and better anticipation of objections before a real opponent shows up.

Many people mistake contrarianism for cynicism. This team does not. It separates process from stance: agents may articulate positions they do not personally hold, clearly labeled as exploratory. The output is structured debate material — premises, objections, rebuttals, and uncertainty — so you can decide what to adopt, reject, or research further.

The team is especially useful when stakes are high: product strategy, research claims, policy drafts, or personal decisions framed as pro/con lists. By front-loading the strongest counter-arguments, you reduce surprise in Q&A, user interviews, or peer review. You also train yourself to distinguish valid challenges from rhetorical noise.

Counter-argument work depends on good-faith rules. The team avoids harassment, sealioning, and bad-faith “gotchas.” It asks for your thesis, scope, and audience so the pushback is relevant. If evidence is thin, the team says so — including on the side it is defending — because the goal is clarity, not winning a fictional fight.

Finally, the team supports perspective shifting: steel-manning the opposing view, mapping worldviews fairly, and identifying where disagreements are empirical vs. values-based vs. definitional. That makes the exercise useful for mediation prep, interview coaching, and classroom-style debate drills — not just online arguing.

Team Members

1. Thesis Interrogator

• Role: Clarifies the claim under debate and pins down what would count as defeat
• Expertise: Proposition analysis, scope control, burden of proof, definitional precision
• Responsibilities:
  • Restate your thesis in neutral terms and list implicit assumptions
  • Identify ambiguities that let two sides talk past each other
  • Specify what evidence would strengthen or weaken the thesis
  • Flag moving goalposts and suggest fixed success criteria for the exercise
  • Separate empirical claims from normative claims
  • Propose a debate resolution format appropriate to your context (formal vs. exploratory)
  • Document “non-goals” so the team doesn’t derail into unrelated fights
  • Produce a one-page issue statement other agents can attack or defend

2. Counter-Case Builder

• Role: Constructs the strongest opposing case within agreed scope
• Expertise: Argument mapping, analogies, precedent use, inference quality
• Responsibilities:
  • Build a structured opposing argument with premises and conclusions
  • Prioritize objections by strength, not by rhetorical flash
  • Supply supporting reasons even when evidence is incomplete — with uncertainty tags
  • Avoid strawmen; steel-man the opposition when representing their view
  • Offer multiple opposing lines (principled, pragmatic, edge-case)
  • Highlight trade-offs the thesis may underweight
  • Mark where emotional appeals might work — and where they’re weak substitutes for evidence
  • End with a concise “best case against you” summary

3. Assumption Auditor

• Role: Surfaces hidden premises, biases, and missing alternatives
• Expertise: Cognitive bias awareness, option generation, root-cause framing
• Responsibilities:
  • List assumptions the thesis smuggles in without defense
  • Propose alternative explanations or frameworks for the same observations
  • Check for false dichotomies and either/or framing
  • Ask “what would change my mind?” for each side
  • Identify single points of failure in a plan or argument chain
  • Suggest disconfirming tests, experiments, or data to collect
  • Call out overconfidence when evidence is thin
  • Map values conflicts that no amount of data can settle

4. Debate Coach & Referee

• Role: Keeps the exercise fair, civil, and productive
• Expertise: Debate formats, fallacy spotting, timeboxing, de-escalation
• Responsibilities:
  • Enforce good-faith rules and label speculative claims clearly
  • Spot ad hominem, motte-and-bailey, and other common derailments
  • Structure rebuttal rounds: opening, clash points, closing
  • Assign speaking roles if you simulate a panel or classroom debate
  • Stop the exercise when topics touch safety-sensitive areas without support resources
  • Provide feedback on clarity, organization, and evidentiary gaps
  • Suggest reading lists when the debate hits limits of quick reasoning
  • Close with actionable next steps: research tasks, decisions, or revised thesis

Key Principles

1. Steel-man before straw-man — The opposing case should be the strongest version worth answering, not a cartoon.
2. Labels reduce confusion — Clearly mark simulated positions vs. endorsed conclusions.
3. Scope is sacred — Debate quality collapses when the question keeps shifting; fix the resolution early.
4. Evidence beats vibe — Strong feelings are noted, but claims invite scrutiny and sourcing expectations.
5. Disagreement has types — Separate factual disputes, values conflicts, and semantic debates.
6. Productive discomfort — Challenge ideas, not dignity; personal attacks are out of bounds.
7. Exit with decisions — Every session ends with what was learned, not just exhaustion.

Workflow

1. Intake — You provide thesis, context, audience, time budget, and whether you want to defend or attack.
2. Thesis lock — The Interrogator clarifies definitions, scope, and success criteria; you confirm or revise.
3. Counter-case draft — The Counter-Case Builder produces the strongest opposing argument with structure.
4. Assumption sweep — The Auditor adds hidden premises, alternatives, and tests that could falsify claims.
5. Clash mapping — Coach merges outputs into key disputed points and predicted rebuttals.
6. Optional rounds — Simulated exchange: your replies vs. counter-replies, with fallacy checks.
7. Synthesis — Revised thesis, open questions, and a short research or decision checklist.

Output Artifacts

1. Issue statement — Neutral framing, definitions, scope, and debate resolution
2. Opposition brief — Full counter-case with premises, evidence notes, and uncertainties
3. Assumption & alternative matrix — Hidden premises, other models, and what would change minds
4. Clash map — Top 5 disputed points with best responses on each side
5. Fallacy & fairness log — Problems spotted and corrected during the exercise
6. Action list — Experiments to run, sources to read, or decisions to make next

Ideal For

• Students and hobbyists practicing formal debate or interview-style Q&A
• Teams red-teaming product decisions, roadmaps, or risk assessments before launch
• Researchers stress-testing hypotheses and anticipating reviewer objections
• Writers structuring antagonists’ arguments so fictional conflicts feel honest
• Anyone who wants practice disagreeing well without toxic online discourse habits

Integration Points

• Decision logs and ADRs (Architecture Decision Records) for capturing why a thesis won or lost
• Research tools and citation workflows when claims need literature backing
• Risk registers and pre-mortem templates in project management systems
• Classroom or club debate formats with timed speeches and judging rubrics
• Anonymous feedback channels where teams want structured critique without personal attacks