Challenge

What Is Challenge?

Challenge is a Claude Code skill designed to rigorously analyze strategic, technical, or business plans before execution. Tagged under productivity, it leverages the pre-mortem analysis framework—a proactive approach that systematically exposes a plan’s hidden risks, faulty assumptions, and overlooked dependencies. The skill’s command syntax is straightforward: /em:challenge <plan>. When invoked, Challenge reviews the provided plan, surfaces its core assumptions, and identifies potential points of failure that could derail the initiative.

Unlike traditional post-mortems, which analyze failures after they occur, Challenge flips the script. It asks users to imagine a scenario where the plan has already failed and then works backward to uncover the causes. The goal is not to criticize for its own sake, but to strengthen the plan so it can survive “contact with reality.”

Repository and source code are available at Claude Skills: Challenge on GitHub.

Why Use Challenge?

Most plans that falter do so not because of random chance, but due to predictable oversights—unexamined assumptions, misjudged dependencies, or underappreciated complexities. Challenge helps mitigate these risks by:

• Surfacing Hidden Assumptions: Many plans implicitly rely on customer behaviors, market conditions, or technical realities that go unstated. Challenge brings these to the forefront.
• Identifying Weak Links: By systematically stress-testing the plan, Challenge exposes dependencies or steps most vulnerable to failure.
• Reducing Confirmation Bias: Teams often fall prey to groupthink or optimism bias, especially when initial feedback is positive. Challenge provides a structured way to inject productive skepticism.
• Improving Stakeholder Confidence: A plan that has undergone thorough pre-mortem scrutiny is more likely to stand up to board, investor, or executive review.

How to Get Started

Integrating Challenge into your workflow is simple. The skill is designed to be invoked via a direct command, typically within a Claude-powered environment. Here’s a step-by-step example:

1. Install or Enable the Skill
   Ensure the Challenge skill is available in your Claude setup. Installation instructions are provided in the GitHub repository.

2. Prepare Your Plan
   Write out your plan in a clear, structured manner. Each section (objectives, strategy, timeline, dependencies, etc.) should be explicit.

3. Invoke the Skill
   Use the command syntax as follows:

   plaintext

   /em:challenge
   Launching a new SaaS platform targeting SMBs. Plan includes: 3-month MVP build, initial marketing via LinkedIn and Google Ads, projected break-even in 9 months, no full-time sales team initially, reliance on organic traffic for first 6 months, partnership with a payment gateway still under negotiation.

4. Review the Output
   The skill will return an analysis that highlights:

   • The core assumptions underlying each plan section
   • Potential failure points
   • Questions and checks to validate assumptions

Key Features

• Pre-Mortem Plan Analysis
  Challenge systematically applies the pre-mortem technique, enabling you to anticipate why a plan might fail before execution.

• Assumption Extraction
  For every plan section, the skill identifies what must be true for the plan to succeed (e.g., “Customers will discover us via organic search”).

• Dependency Analysis
  The skill highlights critical dependencies—such as partnerships, regulatory approvals, or technical integrations—so you can gauge their risk.

• Automated Workflows
  Challenge can be integrated into broader automation pipelines, such as pre-commit hooks, continuous integration checks, or project review workflows.

• Customizable Prompts
  Users can tailor the analysis by providing specific context or areas of concern, allowing for focused reviews.

Practical Example

Suppose your plan includes a new product launch with an untested supply chain. Invoking Challenge would look like this:

/em:challenge
Launching Product X with a new supplier. Assumes 4-week lead times, regulatory compliance in all markets, initial distribution via two logistics partners, and aggressive Q4 sales targets.

Expected output:

• Assumptions: Supplier reliability, regulatory timelines, logistics partner onboarding.
• Risks: Delays in regulatory approval, supply chain disruptions, overestimated demand.
• Validation checks: What if supplier lead times double? What if logistics partner fails to deliver?

Best Practices

• Run Challenge Early and Often: Integrate pre-mortem analysis before major milestones or funding commitments.
• Encourage Diverse Input: Invite team members from different functions to review the Challenge output, as varied perspectives increase coverage.
• Document Outcomes: Record which assumptions and risks were identified, and track actions taken to mitigate them.
• Pair With Other Reviews: Challenge complements, but does not replace, standard risk assessments or technical reviews.

Important Notes

• Not a Replacement for Due Diligence: While Challenge is a powerful tool, it should augment—not replace—comprehensive risk and feasibility analysis.
• Quality of Input Matters: The depth of the analysis depends on the clarity and detail of the plan provided.
• Handles Textual Plans: The skill is optimized for text-based plans; highly visual or diagrammatic plans may require adaptation.
• Bias Mitigation: Challenge is designed to inject skepticism, but teams must remain open to revising assumptions and plans in response to identified weaknesses.

By systematically deploying Challenge, teams can fortify their plans against predictable failure, creating a culture of constructive scrutiny and adaptive planning.