devils-advocate

Run three parallel critics and synthesize adversarial findings into a report.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/RawleySM/rlm-adk --skill devils-advocate-rawleysm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devils-advocate
Source: https://github.com/RawleySM/rlm-adk/tree/main/.claude/skills/devils-advocate
Command: npx skills add https://github.com/RawleySM/rlm-adk --skill devils-advocate-rawleysm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates a team of three specialized critics to stress-test a subject from multiple adversarial angles, surface blind spots, and surface opportunities before committing to implementation.

Core Features & Use Cases

  • Three parallel critics (ADK Callback Expert, Vision Alignment Challenger, Prior-Art Researcher) evaluate the subject from distinct angles and produce findings that are synthesized into a single actionable report.
  • Stepwise process: determine subject, spawn critics in parallel, synthesize into a final report for decision-makers.
  • Use cases include evaluating plans, proposals, or code when a critical review, blind-spot discovery, or sanity check is needed before committing resources.

Quick Start

Spawn the three critics, feed them the subject, and receive a consolidated critique report.

Frequently Asked Questions about devils-advocate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an adversarial review on a software engineering plan before committing resources?

An adversarial review stress-tests a subject by spawning three parallel critics—a callback expert, a vision alignment challenger, and a prior-art researcher—to surface blind spots. The synthesized report provides actionable improvements for decision-making before implementation.

What is a parallel-agent critical-thinking analysis for code and proposals?

A parallel-agent critical-thinking analysis orchestrates multiple specialized critics concurrently to evaluate a subject from distinct adversarial angles. It targets gap discovery and risk analysis, consolidating findings into a unified report for sanity checking plans and proposals.

Can I use inline text and file paths as input for a risk analysis critique?

Yes, the risk analysis critique accepts file paths, code snippets, or inline text as the subject. The system reads the provided input and feeds it directly to the three parallel critics for evaluation.

What's the best way to identify blind spots in a technical proposal?

The best way to identify blind spots is running a multi-angle adversarial critique. By evaluating the proposal through callback validation, vision alignment, and prior-art research lenses in parallel, you surface gaps and practical improvements before committing.

Does the adversarial critique process require any external dependencies?

No, the adversarial critique process operates without external dependencies. It requires only the subject material—inline text, code, or a file path—to spawn the specialized critics and synthesize the consolidated findings.