Individual skill

devils-advocate

Systematically challenge current assumptions before major decisions. Counters confirmation bias, groupthink, and overconfidence.

plugins/mycelium/skills/devils-advocate/SKILL.md

Read pinned source

Source commit d44421b0667bb71ad515ae7576dfc0f47b00504f

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 51
Repository last updated: Nov 6, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-code Repository topic
ai-agent Repository topic
delivery Repository topic
devops Repository topic
discovery Repository topic
product-development Repository topic
product-management Repository topic
claude-code-skills Repository topic
dora-metrics Repository topic
product-discovery Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 13,754 bytes

Read excerpt


# Devil's Advocate

Run before every major diamond transition and architecture decision. Source: Kahneman, Shotton.

## Technique 1: Pre-Mortem
Imagine it's 6 months from now and this decision FAILED spectacularly.
1. What went wrong?
2. What assumption was the weakest link?
3. What signal did we ignore?
4. Who was affected and how?

## Technique 2: Assumption Reversal
For each key assumption:
- State the assumption explicitly