Challenge

Looking at what's provided, this appears to be a C-level advisor skill designed to push back on your thinking when you're in decision-making mode. The idea is straightforward: you bring a strategic decision or direction, and it questions your assumptions, pokes holes in your logic, and surfaces risks you might be glossing over. It's useful when you're working through high-stakes choices and need someone to play devil's advocate without the politics. The source material is minimal, so I can't speak to specific frameworks or question patterns it uses, but the core concept is solid if you tend to convince yourself too easily or work in an echo chamber.

skills.sh installs: 1.4K
GitHub stars: 29.5K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add alirezarezvani/claude-skills --skill challenge --agent claude-code

Installs into .claude/skills of the current project.

Files

/executive-mentor:challenge — Pre-Mortem Plan Analysis

Command: /executive-mentor:challenge <plan>

Systematically finds weaknesses in any plan before reality does. Not to kill the plan — to make it survive contact with reality.

The Core Idea

Most plans fail for predictable reasons. Not bad luck — bad assumptions. Overestimated demand. Underestimated complexity. Dependencies nobody questioned. Timing that made sense in a spreadsheet but not in the real world.

The pre-mortem technique: imagine it's 12 months from now and this plan failed spectacularly. Now work backwards. Why?

That's not pessimism. It's how you build something that doesn't collapse.

When to Run a Challenge

Before committing significant resources to a plan
Before presenting to the board or investors
When you notice you're only hearing positive feedback about the plan
When the plan requires multiple external dependencies to align
When there's pressure to move fast and "figure it out later"
When you feel excited about the plan (excitement is a signal to scrutinize harder)