Agent skill
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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/cursor-debate
SKILL.md
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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?