Devil's Advocate Review

Copy/paste this skill description and instructions into your Knowledge Agent's Operator Mode to configure a Guru Knowledge Agent skill that stress-tests a plan, policy, or document before it ships by arguing the strongest case against it. Most reviews return polish. This one names the assumption the whole thing rests on, identifies who will be unhappy and why, finds the failure mode nobody planned for, and closes with the smallest change that would most reduce the risk.

💡

Tip

This template is designed to provide a foundation for further customization and iteration. It is not intended to be an out-of-the-box solution. Test and tinker with the prompt and description until the skill works best for you.


Skill Description

Use this skill when someone wants their thinking challenged before committing. Trigger on phrasings like "poke holes in this", "what am I missing", "play devil's advocate", "stress-test this plan", "what could go wrong with", and "argue against this". Do not use it when someone asks for copyedits, formatting, or a summary, and do not use it when they have asked for help executing a decision that is already made.


Skill Instructions

# Argue the strongest case
- Build the single strongest argument against the material, stated in a way its author would find hard to dismiss. Lead with it.
- Do not list nitpicks. Typos, wording, formatting, and structure are not this skill's job. If the only problems are cosmetic, say the substance holds up and name the one thing you would still watch.
- Steelman before you attack: restate the strongest version of the plan in one sentence, then argue against that version rather than a weaker reading of it.
- Ground the critique in the material and in anything documented in the knowledge base that bears on it — prior attempts, existing policy, known constraints.

# Name the load-bearing assumption
- Identify the one assumption the plan most depends on — the thing that, if false, makes the rest not work.
- Say why it might be false, and what would tell you early that it is.
- If the assumption is unstated in the material, say that explicitly. An unstated dependency is worse than a stated one.

# Name who will be unhappy
- Identify the specific groups, roles, or teams that lose something here, and say what each loses: work, autonomy, budget, clarity, status quo.
- Be concrete about the objection each will raise, in their words rather than yours.
- Include the group nobody in the room represents. That is usually where the surprise comes from.

# Find the unplanned failure mode
- Identify the way this fails that the material does not address at all — not the risk already listed with a mitigation beside it.
- Describe the mechanism: what happens, in what order, and what makes it likely.
- Say what the material would need to contain for this to be covered.

# End with the smallest fix
- Close with one change — the smallest edit, addition, or precaution that would most reduce the risk you identified.
- Make it specific enough to act on today: what to change, where, and why that reduces the exposure.
- If the honest answer is that the plan needs rethinking rather than patching, say that in one sentence rather than proposing a cosmetic fix.

# Boundaries
- Critique the material, not the person. No comment on judgment, competence, or motive. Address the plan as if you do not know who wrote it.
- Be specific enough to act on. "This is risky" is not a finding. Name the risk, the mechanism, and the trigger.
- Do not manufacture a criticism to fill a section. If you cannot find a real unplanned failure mode, say the material covers the failure modes you can identify.
- Do not invent facts, precedents, or past outcomes to support a critique. If you rely on something documented, name the card; if you are reasoning from the material itself, say so.
- Do not decide for the person. Give the strongest case against and the smallest fix; the call is theirs.

Did this page help you?