devil-advocate

Analyze decisions and architectures for risks, alternatives, and reversibility.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/igorder-dev/apex --skill devil-advocate-igorder-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devil-advocate
Source: https://github.com/igorder-dev/apex/tree/main/.claude/skills/devil-advocate
Command: npx skills add https://github.com/igorder-dev/apex --skill devil-advocate-igorder-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured devil's advocate analysis of decisions, technology choices, and architectures to stress-test approaches before committing to them in documentation.

Core Features & Use Cases

  • Level 1: Decision Critique — unbiased, steel-man first critique of the strongest version of the current position.
  • Level 2: Scope Critique — run after every document to surface forgotten requirements, failure modes, and implicit needs.
  • Level 3: "First Day on the Job" Test — ensures a new reader can set up and use the doc pack without questions.
  • Minimum Gaps Rule — forces identification of at least two potential gaps per document (or explicitly state no gaps).
  • Tone and Deliverable — provides a respectful, evidence-based verdict with actionable next steps.

Quick Start

Provide a structured devil's advocate critique of the given decision, highlighting risks, alternatives, and reversibility.

Frequently Asked Questions about devil-advocate

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

FAQPage Schema
How do I critique architecture decisions and surface hidden risks before committing to documentation?

To critique architecture decisions, apply a structured devil's advocate analysis that steel-mans the strongest version of your position, surfaces risks and alternatives, and enforces a minimum gaps rule to identify at least two forgotten requirements per document.

What is a devil's advocate analysis for technology choices and build-vs-buy discussions?

A devil's advocate analysis for technology choices is a structured critique that stress-tests build-vs-buy decisions by surfacing implicit needs, evaluating reversibility, and delivering an evidence-based verdict with actionable next steps.

How do I run a design review to ensure a new reader can use the documentation without questions?

Run a "First Day on the Job" test during design review to ensure a new reader can set up and use the document pack without questions, verifying that scope critique has surfaced all implicit needs and failure modes.

Can I use this approach to find gaps in Architecture Decision Records (ADRs)?

Yes, you can apply devil's advocate critique directly to ADRs to surface forgotten requirements, evaluate trade-offs, and enforce the minimum gaps rule, which requires identifying at least two potential gaps or explicitly stating none exist.

What are the limitations of devil's advocate critique for risk analysis?

Devil's advocate critique for risk analysis is limited to surfacing risks, alternatives, and reversibility in documentation; it provides a respectful, evidence-based verdict with next steps but does not make the final implementation decision for the team.