devils-advocate

Identify flaws and surface risks in design documents and decisions.

8|5|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/axiomantic/spellbook --skill devils-advocate-axiomantic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devils-advocate
Source: https://github.com/axiomantic/spellbook/tree/main/skills/devils-advocate
Command: npx skills add https://github.com/axiomantic/spellbook --skill devils-advocate-axiomantic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Devil's Advocate techniques help teams surface unchallenged assumptions and hidden risks early in design processes, reducing post-release incidents.

Core Features & Use Cases

  • Structured challenge framework focusing on assumptions, scope, architecture, integrations, and edge cases.
  • Evidence-driven critique requiring explicit flags and justification.
  • Pre-implementation reviews for design docs, architecture decisions, and concept validation.

Quick Start

Provide a design document and request a structured devil's-advocate critique to surface risks.

Frequently Asked Questions about devils-advocate

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

FAQPage Schema
How do I identify unvalidated assumptions in a design document?

Use a devil's-advocate critique to surface unvalidated assumptions in a design document by enforcing evidence-based review with explicit flags for scope, architecture, integrations, edge cases, and success criteria.

What is the best way to analyze risks in architecture decisions before implementation?

The best way to analyze risks in architecture decisions is requesting a structured devil's-advocate critique that applies evidence-driven challenge logic to surface hidden flaws and unvalidated assumptions early.

How do I review design documents to surface hidden flaws and edge cases?

Review design documents by applying evidence-driven critique with explicit flags for assumptions, scope, architecture, integrations, edge cases, and success criteria to surface hidden flaws and reduce post-release incidents.

When do I need a devil's advocate review for my design process?

You need a devil's advocate review during pre-design discussions, architecture decisions, and design doc reviews to surface unchallenged assumptions and hidden risks early in the design process.

Does design review work without evidence-based critique and explicit flagging?

Design review without evidence-based critique risks missing unvalidated assumptions, whereas a structured devil's advocate approach enforces explicit flagging and justification to surface hidden flaws and reduce post-release incidents.