agentleFS
anxndsgnanxndsgn/skills/debate/SKILL.md

debate

Skill1 starsChanged 51 days agoApache-2.0View on GitHub

Adversarially validate a product idea against reality — two parallel agents build the strongest evidenced case for and against it, then the main thread rules on evidence quality. Use when the user asks whether an idea is actually worth building, wants it validated with real evidence rather than conversation, or a big idea emerges from /talk-about-an-idea with stakes high enough to justify two research agents.

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use handoff, commit and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 5 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 3 projects that use this

The file

Files
SKILL.md

/debate <idea> → two agents with opposing briefs in parallel → verdict on evidence quality

A single researcher investigating an idea mostly finds evidence for their first impression — motivated search is invisible from the inside. Splitting the search into two opposing briefs makes the bias work for you: each side hunts hard, and only evidence that survives the other side's case earns a place in the verdict.

The input is a crisp idea — problem, person, wedge. If it's still fuzzy, clarify it first (that's /talk-about-an-idea's job); debating a vague idea just produces two piles of unrelated links.

The two briefs

Launch both agents in a single message so they run concurrently. Neither gets a persona or a prior — just an opposing brief. Each brief includes the idea verbatim, the research discipline quoted verbatim (an agent can't follow rules it never sees) — every claim links to its source, evidence stays separate from inference, findings carry dates — and /research's method as the toolbox: go wherever the answer leaves a first-hand trace, and treat secondary accounts as leads, not evidence.

  • For — the strongest honest case that this is worth building: demand behavior, people paying for inferior substitutes, recurring complaints about the status quo, gaps competitors leave open.
  • Against — the strongest honest case that it isn't: dead or struggling competitors who tried, users content with the workaround, structural moats, evidence the pain is mild or shrinking.

"Strongest honest case" means advocate, don't fabricate — evidence each side searched for and couldn't find is part of its case, and each returns that too.

The verdict

Both sides will always find something, so never count evidence — weigh it. Observed behavior (paying, switching, building workarounds) outranks complaints; complaints outrank opinion pieces; recent outranks stale; independent sources corroborating outrank one loud voice. The verdict rests on which case's best evidence survives the other case.

## Debate: <idea>

**Verdict:** <worth building / not worth building / hinges on <the one unresolved question>>

## The case for
<its surviving evidence, sourced>

## The case against
<its surviving evidence, sourced>

## What would change the verdict
<the concrete evidence that would flip it, and where to look>

Close with the verdict and stop — whether to proceed is the user's call. A "worth building" flows into /grill-me → /to-spec; a "hinges on" names the experiment to run first.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.