| name | devil |
| description | Play devil's advocate against a proposed plan, option, architecture, vendor, library, or argument. Use to counter sycophancy and surface risks before committing. |
Devil Skill
Goal
Produce a rigorous contrarian critique of the current proposal.
Use when the user says:
/devil
/devil 5
play devil's advocate
attack this plan
what am I missing?
stress-test this
give me objections
Critique count
If the user provides a number, produce exactly that many critique points.
If no number is provided, produce 5.
Critique style
Be direct, specific, and evidence-seeking.
Each critique point should include:
### <number>. <Risk title>
**Objection:**
...
**Why it matters:**
...
**Failure mode:**
...
**How to test or de-risk:**
...
Domains to check
For software/agentic projects, inspect:
- maintenance risk
- dependency risk
- security risk
- repo maturity
- API fragility
- hidden operational cost
- data/privacy risk
- scaling bottlenecks