pedrohcgs/claude-code-my-workflow

devils-advocate

Adversarial 5-7 question challenge to a deck's pedagogical choices — ordering, prerequisites, cognitive load, motivation.

First seen Feb 19, 2026

Installation

$ npx skills add pedrohcgs/claude-code-my-workflow --skill devils-advocate

Summary

  • Adversarial 5-7 question challenge to a deck's pedagogical choices — ordering, prerequisites, cognitive load, motivation.
  • Use when user says "devil's advocate", "poke holes in this deck", "push back on my slides", "stress-test the design", "what would a skeptical student ask?".
  • Read-only; surfaces questions to force rethinking.
  • Lighter than `/pedagogy-review`.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from pedrohcgs/claude-code-my-workflow · top by installs.

npx skills add pedrohcgs/claude-code-my-workflow

Browse all from pedrohcgs/claude-code-my-workflow

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1.6K
License LICENSE
Default branch main
Open issues 3
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Grep, Glob
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,566 B
  • docs SUMMARY.md 387 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 51 installs

SKILL.md

Devil's Advocate Review

Critically examine a slide deck and challenge its design with 5-7 specific pedagogical questions.

Philosophy: "We arrive at the best possible presentation through active dialogue."


Setup

  1. Read the target file (the lecture being challenged)
  2. Read the knowledge base in .claude/rules/ for notation conventions and narrative arc
  3. If applicable, read adjacent lectures for narrative continuity

Challenge Categories

Generate 5-7 challenges from these categories:

1. Ordering Challenges

"Could students understand this better if we showed X before Y?"

2. Prerequisite Challenges

"Do students have the background for this notation at this point?"

3. Gap Challenges

"Should we include an intuitive example before this formal proof?"

4. Alternative Presentation Challenges

"Here are 2 other ways to visualize/present this concept."

5. Notation Conflict Challenges

"This symbol conflicts with earlier lecture usage."

6. Cognitive Load Challenges

"This slide has too many new symbols. Can we split?"

7. Book Vision Challenges

"If this becomes a book chapter, does this section stand alone?"


Output Format

# Devil's Advocate: [Lecture Title]

## Challenges

### Challenge 1: [Category] — [Short title]
**Question:** [The specific pedagogical question]
**Why it matters:** [What could go wrong]
**Suggested resolution:** [Specific action]
**Slides affected:** [Numbers or titles]
**Severity:** [High / Medium / Low]

[Repeat for 5-7 challenges]

## Summary Verdict
**Strengths:** [2-3 things done well]
**Critical changes:** [0-2 changes before teaching]
**Suggested improvements:** [2-3 nice-to-have changes]

Principles

  • Be specific: Reference exact slides and notation
  • Be constructive: Every challenge has a suggested resolution
  • Be honest: If the deck is good, say so
  • Prioritize: Notation conflicts > missed metaphors
  • Think like a student: Where do they get lost?