Stress Test

What Is Stress Test?

The Stress Test skill is a focused business analysis tool designed for developers, product leaders, and founders who want to proactively challenge and validate their most critical business assumptions. Available as the /em:stress-test <assumption> command, this skill systematically deconstructs a stated business belief—such as revenue projections, market size, or customer retention—and rigorously tests it for hidden risks before those assumptions are exposed in the real world. Instead of waiting for the market to invalidate your business model, the Stress Test skill empowers teams to identify vulnerabilities early, refine their strategies, and improve decision-making accuracy.

Why Use Stress Test?

Most startups and organizations operate under a cloud of optimistic assumptions. While optimism fuels innovation, it often results in unchecked beliefs that can jeopardize a business. For example, overestimating a market’s size may lead to inflated revenue forecasts, which in turn can mislead hiring, fundraising, and product investment decisions. The Stress Test skill prevents these scenarios by:

• Highlighting Hidden Risks: It exposes weaknesses in business logic that may otherwise go unquestioned.
• Increasing Team Calibration: By making assumptions explicit and testable, team discussions become more grounded and evidence-driven.
• Enhancing Investor Confidence: Demonstrating a rigorous approach to business planning builds trust with stakeholders and potential investors.
• Reducing Cognitive Bias: The skill acts as a counterweight to groupthink and confirmation bias, two common pitfalls in startup environments.

By systematically breaking down and analyzing assumptions, the Stress Test skill helps prevent costly mistakes and supports sustainable growth.

How to Get Started

The Stress Test skill is open-source and can be integrated as part of a development or executive advisory workflow. To get started:

1. Installation: Clone or download the skill from the official GitHub repository.

   bash

   git clone https://github.com/alirezarezvani/claude-skills.git
   cd claude-skills/c-level-advisor/executive-mentor/skills/stress-test

2. Command Usage: The core interface is the /em:stress-test command, which accepts a single, explicit business assumption as its argument.

   plaintext

   /em:stress-test The total addressable market for B2B spend management software in German SMEs is €2.3B

3. Integration: The skill can be used interactively in chat-based executive mentoring platforms or embedded into internal advisory bots for ongoing business planning.

4. Customization: The skill’s logic can be extended or tailored to fit specific business domains or workflow integrations.

Key Features

• Explicit Assumption Analysis: Converts vague beliefs into concrete, falsifiable statements. For example, instead of “our churn is low,” the skill pushes the team to specify, “monthly customer churn will not exceed 3% over the next 12 months.”
• Domain-Agnostic: Applicable to a broad range of business assumptions, including market sizing, customer retention, hiring velocity, and pricing.
• Structured Stress Testing: Applies a systematic methodology to interrogate the plausibility, supporting evidence, and potential failure points of the stated assumption.
• Rapid Scenario Generation: Facilitates “what if” analyses by simulating adverse conditions—such as lower-than-expected conversion rates or higher-than-modeled churn.
• Actionable Output: Provides recommendations for data gathering, risk mitigation, or model adjustments based on the test results.

Example:

Stress Testing a Revenue Projection

/em:stress-test Our SaaS platform will reach $2M ARR by December with a 5% monthly growth rate and 90% logo retention.

Typical output may include:

• Probing questions about growth rate evidence and historical validation.
• Simulated scenarios where churn rises or acquisition slows.
• Suggestions to validate assumptions with early customer data or market research.

Best Practices

• Isolate and Specify: Never test broad statements. Break down each business model component into specific, measurable assumptions.
• Document Rationale: Record the source and reasoning behind each assumption for future reference and accountability.
• Iterate Frequently: Use the skill regularly as new data emerges or as the business context changes.
• Engage the Team: Make stress-testing a collaborative exercise to uncover blind spots and build a culture of constructive skepticism.
• Integrate with Planning: Embed the skill into strategic planning, board meeting prep, and investor communications for ongoing calibration.

Important Notes

• Stress Testing ≠ Pessimism: The goal is not to undermine confidence, but to ensure preparedness for a range of outcomes.
• Requires Honest Input: The value of the skill depends on the specificity and realism of the assumption being tested.
• Not a Substitute for Data: While it’s a powerful qualitative tool, stress testing should be complemented with quantitative research and market validation.
• Customization Recommended: Tailor the skill’s prompts and logic to the unique characteristics of your market, product, or team dynamics.
• Open Source License: The Stress Test skill is distributed under an open-source license, allowing for modification and integration into proprietary tools.

By embedding the Stress Test skill in your business analysis workflow, you empower your team to identify and address the assumptions most likely to impact your success—before the market does.