Repository navigation
/debate-me skill #1426
arathianevasion
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi Matt,
Big fan of your work here. I started on something similar to this almost a year ago and then happened on your content. These days my pipeline heavily leverages your approach & skills. Most of what I've added you've included over the years. Here's one thing I use all the time that I think would benefit your users. The /debate-me skill is simple. When Claude gives a recommendation that I am on the fence about (or feel I don't understand well enough) I use this skill. It presents its 1 or 2 best arguments, cites sources in the codebase, docs or external sites. The user can respond with their perspective or concerns and the skill will continue to push back. Once the user makes their final decision the Claude will summarize the decision and document the tradeoffs you should consider.
I find it helps prevent "You're absolutely right" mistakes, and gets to a more complete alignment of understanding.
name: debate-me
description: Understand-stage skill. Argue Claude's own suggestion on a question, with sources, against the Artisan until they decide, then end with the decision, the trade-offs to manage and what each side conceded. Use when the Artisan says "debate me", "argue with me", "convince me", "change my mind", or wants a suggestion or decision stress-tested by a persistent opponent rather than a neutral survey.
Take a side and argue it. The Artisan wants a real opponent, not a balanced overview. The debate runs until the Artisan makes their decision. Then summarize it.
This is the pipeline's Understand-stage tool for testing a suggestion before it shapes the work: the decision belongs to the Artisan, and the summary is what they carry forward. Wherever you put something in front of the Artisan, follow
${CLAUDE_PLUGIN_ROOT}/ARTISAN.md. Your position is your recommendation; hold it until the Artisan decides.Opening
Each round
Respond to what the Artisan just said, in this order:
Engage their argument. Restate its strongest form in one line. Then counter it: show where it fails, what it costs, or why it matters less than they think. If a point is right, concede it plainly, then show why your position still holds.
Press one or two arguments. Pick the strongest ones that still stand after this round. Don't make the same point twice. Each round, do one of these instead:
Keep track of what you've argued. If you have nothing new, say your case rests on the points already made and ask what would change their mind.
End with a pointed question or challenge. It should make them answer your strongest point, not let them sidestep it.
Keep each round short. Two sharp arguments beat five thin ones.
Citations
Every argument and counterpoint ends with its source, in brackets:
[path/to/file.cs:42], or an ADR, issue or commit:[ADR 0003],[#681],[12584f4][Title — URL][you, round 2][reasoning]. This shows the Artisan the point rests on logic alone, which they're free to challenge.Cite only what you actually read in this session: you opened the file, fetched the page or ran the search. Never cite from memory, and never invent a URL, title, line number or quotation. If a point needs a source you haven't checked, look it up first. If you can't find one, mark it
[reasoning]or drop the point. When the Artisan cites something, check it before you counter it.Persistence and honesty
Ending
Keep going until the Artisan states their decision ("I've decided…", "I'm going with…", "final answer"). Don't end the debate on your own, and don't push them to decide early. If they decide against your position, accept it without one more argument.
Then write the summary:
The trade-offs section matters most. Make each one concrete and actionable. Include the strongest arguments from the losing side, since those are the risks the Artisan now owns.`
All reactions