agents/skills/devils-advocate/SKILL.md
Execute the /devils-advocate workflow shared across Codex, Claude Code, and Copilot in this repository. Use when you want to stress-test ideas, challenge assumptions, or play devil's advocate.
npx skillsauth add drn/dots devils-advocateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Critically evaluate proposals, plans, and arguments to identify weaknesses and offer alternative perspectives.
You are acting as a rigorous Devil's Advocate. Your job is to stress-test ideas, not to be contrarian for its own sake, but to help arrive at better solutions through critical analysis.
First, summarize the core proposal in 2-3 sentences to confirm understanding. Identify:
Look for common reasoning errors:
Causal Fallacies
Assumption Fallacies
Evidence Fallacies
Process Fallacies
For each major assumption in the proposal, ask:
Consider stakeholders or viewpoints not represented:
Offer 2-3 alternative ways to frame the problem or solution:
For each criticism you raise, also present the strongest defense of the original proposal. This ensures fair analysis.
Conclude with:
# Devil's Advocate Analysis
## Proposal Summary
{2-3 sentence summary of what's being proposed}
## Logical Fallacies Detected
### {Fallacy Name}
**Where it appears**: {quote or reference}
**Why it's problematic**: {explanation}
**Steelman defense**: {strongest counter to this criticism}
## Challenged Assumptions
### Assumption: "{assumption}"
- **Evidence for**: {what supports this}
- **Evidence against**: {what contradicts this}
- **Breaking conditions**: {when this assumption fails}
## Missing Perspectives
| Stakeholder | Their Likely View | Why It Matters |
|-------------|-------------------|----------------|
| {who} | {what they'd say} | {impact} |
## Alternative Framings
### Frame 1: {name}
{description of alternative approach}
### Frame 2: {name}
{description of alternative approach}
## Synthesis
### Top 3 Concerns
1. {concern with brief explanation}
2. {concern with brief explanation}
3. {concern with brief explanation}
### Suggested Modifications
- {modification 1}
- {modification 2}
### Questions to Answer
- {question 1}
- {question 2}
### Overall Assessment
{Honest evaluation: Is this fundamentally sound? Should it proceed with modifications? Or needs rethinking?}
development
Build a self-contained, single-file HTML presentation deck from talking points or a source doc, using a terminal/TUI-styled template with keyboard, tap, and swipe navigation. Use when the user wants to create slides, build a presentation or deck, turn talking points or a doc into a talk, make an HTML slideshow, or produce a presentation as a shareable artifact (instead of Google Slides).
development
Render a Markdown file to GitHub-flavored HTML and open a styled local preview (light + dark) in the browser. Use when the user wants to preview markdown, see how a README renders on GitHub, check that relative screenshots or images display correctly, or get a GitHub-like local preview without installing grip or glow.
tools
Mark the current Argus task as complete. Use when the work for the current worktree is done and the user wants the task to transition to the "complete" status.
development
Launch a dynamic Workflow where the top-tier session model (Fable) handles planning and orchestration while implementation subagents run on Sonnet for routine tasks and Opus for complex ones. Use when the user wants to orchestrate a build, a dynamic workflow, a model-tiered build, fable planning with sonnet and opus implementation, or tiered agents.