From python
Structured critical thinking for challenging approaches, questioning assumptions, and validating decisions. Use when testing approach validity or preventing automatic agreement.
How this skill is triggered — by the user, by Claude, or both
Slash command
/python:oracle-challengeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<strategist>
Analyze the challenge request: $ARGUMENTS
Challenge Extraction:
Challenge Summary: You're challenging: [identified approach] Because: [extracted concern] In context of: [session context]
Critical Thinking Prompts:
Use sequential thinking (mcp__sequential-thinking__sequentialthinking) to analyze this challenge:
Thought 1: Question the fundamental assumptions Thought 2: Examine contradictory evidence Thought 3: Explore alternative approaches Thought 4: Assess context-specific fit Thought 5: Evaluate risks and trade-offs Thought 6: Synthesize findings into recommendation
Build systematically through evidence, alternatives, and risks. Continue until you reach a clear conclusion.
Self-Critique Questions:
Final Synthesis:
Challenge Technical Decisions:
/atelier-challenge "Do we really need a microservices architecture for this simple app?"
Challenge Implementation Approach:
/atelier-challenge "I think this caching strategy will actually slow things down"
Challenge Requirements:
/atelier-challenge "Are we solving the right problem with this feature?"
Challenge Architectural Patterns:
/atelier-challenge "Should we really use event sourcing for this use case?"
Before Major Decisions:
When Something Feels Off:
To Prevent Automatic Agreement:
Use /atelier-challenge: Question assumptions, test validity, assess risks, prevent automatic agreement Use /atelier-thinkdeep: Deep exploration, comprehensive analysis, alternative discovery, complex decisions
Key distinction: Challenge = critical evaluation, ThinkDeep = deep exploration
npx claudepluginhub martinffx/atelier --plugin codePressure-tests assumptions, decisions, or inherited constraints via Socratic cross-examination. Asks one question at a time to expose weak reasoning, cargo-culting, and untested instincts, then delivers a verdict.
Challenges claims by verifying accuracy, completeness, and reasoning against code, docs, or data. Use for sanity-checking decisions, evaluating assertions, or 'are you sure?' prompts.
Facilitates Socratic questioning to surface assumptions, challenge positions, debug mental models, and resolve uncertainty in decisions, designs, or debugging.