cursor-debate

Run a research-first, multi-perspective debate to explore complex technical decisions (trade-offs, architecture choices, integration strategies) using concrete codebase evidence. Use when the user asks to "debate" approaches, compare options, or needs a structured exploration before deciding.

⭐6stars🔀2forks📁View on GitHub🕐Updated Jan 5, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill facilitates evidence-based technical decision-making through a structured, multi-perspective debate framework. By analyzing real codebase evidence, it helps developers and architects explore complex trade-offs, integration strategies, and system design choices to ensure robust and informed engineering outcomes.

Use Cases

  • Evaluating Architectural Trade-offs: Compare competing system designs, such as choosing between a monolithic or microservices approach, by simulating expert personas and citing specific codebase constraints.
  • Integration Strategy Planning: Determine the most efficient way to incorporate new third-party APIs or internal modules by researching existing patterns and debating the impact on system stability.
  • Refactoring vs. Rewrite Decisions: Conduct a research-first exploration to analyze technical debt using 'git log' and repository inspection to decide the best path for legacy code modernization.
  • Complex Tooling Selection: Use the debate round to compare different libraries or frameworks based on how well they align with the current project's architecture and performance requirements.
  • Objective Conflict Resolution: Resolve engineering team disagreements on implementation details by providing a structured, multi-perspective analysis that surfaces hidden risks and benefits.
namecursor-debate
descriptionRun a research-first, multi-perspective debate to explore complex technical decisions (trade-offs, architecture choices, integration strategies) using concrete codebase evidence. Use when the user asks to "debate" approaches, compare options, or needs a structured exploration before deciding.

Cursor Debate

Overview

Structure an evidence-based “debate round” to surface ideas and trade-offs; the debate does not decide, it informs the human decision-maker.

Workflow

1) Define the question

  • Write the precise decision question (1 sentence).

2) Choose candidates

  • Include 3–6 perspectives total.
    • Human personas (pragmatist, architect, researcher, integrator, tool builder)
    • Optional “code entity” personas (actual modules/symbols), backed by real file evidence

3) Research first (required)

  • For each candidate, list questions they need answered.
  • Run concrete repo inspection (examples):
    • rg -n "...", git grep, git log -p -- <path>, go test ./..., etc.
  • Record commands + key outputs in “Pre-Debate Research”.

4) Debate round

  • Opening statements (Round 1)
  • Rebuttals (Round 2)
  • Moderator summary (tensions, trade-offs, open questions)

Output template

Use the canonical outline in references/debate.md.