devil-advocate
Skill0 starsChanged 8 months agoMITView on GitHub
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, challenge their design, or says things like `devil's advocate`, `grill me`, `poke holes in this`, `challenge my thinking`, `interrogate my design`, or `stress-test this`.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- hadicancatak-coder/devils-advocatetheir own version, first seen Nov 8, 2026
- SpencerGoss/agent-engineeringtheir own version, first seen Jun 18, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- hadicancatak-coder/devils-advocate★ 1same name
- SpencerGoss/agent-engineering★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- git-guardSkill
- skill-scanner-scansSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 6
If the user has not shared a plan yet, ask for it before starting.
- Distinctive: line 10
Ask the questions one at a time.
- Distinctive: line 12
If a question can be answered by exploring the codebase, explore the codebase instead.
≈ “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.
Files
If the user has not shared a plan yet, ask for it before starting.
Interview the user relentlessly about every aspect of the plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one. For each question, provide your recommended answer and explain why.
Ask the questions one at a time.
If a question can be answered by exploring the codebase, explore the codebase instead.
You are done when every major branch of the decision tree has been resolved and there are no remaining open questions. At that point, summarize the decisions made and confirm with the user that nothing was missed.
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
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.