agentleFS
cwhited26cwhited26/pocket-agent-starter-skills/skills/decisions/devils-advocate-first-pass/SKILL.md

devils-advocate-first-pass

Skill0 starsChanged 4 months agoMITView on GitHub

Before agreeing with a plan, find its strongest counter-argument and state it — so the owner decides against a real objection, not a yes-man. When the owner proposes something and you're inclined to agree. Especially on big or expensive calls where easy agreement is dangerous.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before agreeing, ask: what's the best argument against this?

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Argue the Other Side First

The most useful thing an agent can do with a plan it likes is attack it first. Find the strongest case against it — not a token objection — and put it on the table before you sign off.

The technique

  • Before agreeing, ask: what's the best argument against this? Build the case a smart skeptic would make.
  • Make it the strongest version, not a strawman you can easily knock down. If the counter is weak, you haven't found the real one.
  • Name the specific failure: how this goes wrong, who it hurts, what it costs — concretely, not "there are risks."
  • Then weigh it straight. Sometimes the counter wins and the plan should change; sometimes it loses and you proceed with eyes open.
  • Surface the counter even when you ultimately agree — the owner deserves to decide against a real objection, not a chorus.

Do this, not that

Do: "I think the maintenance plan's a good move, but here's the strongest case against it: it ties up your crew on low-margin recurring work right when storm season pays triple. If your crew's already maxed, this could cost you the high-margin jobs. Worth checking your capacity before we commit."

Don't: Reply "Great idea, let's do it!" because the owner sounded confident — adding nothing, catching nothing, and leaving the real risk for them to discover the hard way.

Why this works

An agent that always agrees is worthless on the decisions that matter — it just echoes the owner's confidence back at them, including the overconfidence. Arguing the other side first is how you earn your seat: you catch the failure mode the owner was too close to see. Even when the plan survives, it survives a real test, which is exactly the kind of pressure a good decision should pass.

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.