scenario-and-sensitivity-analysis

Stress-test financial forecasts with scenario bundles and single-variable sensitivity sweeps.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/fritzgeraldz/Vibe-Managing --skill scenario-and-sensitivity-analysis-fritzgeraldz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scenario-and-sensitivity-analysis
Source: https://github.com/fritzgeraldz/Vibe-Managing/tree/main/skills/finance/scenario-and-sensitivity-analysis
Command: npx skills add https://github.com/fritzgeraldz/Vibe-Managing --skill scenario-and-sensitivity-analysis-fritzgeraldz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Founders commit to budgets, fundraising, and major bets without knowing how much room for error their financial plan has or which assumption would break it first. This Skill stress-tests a base-case forecast by building coherent Base/Upside/Downside scenarios and running single-variable sensitivities to expose the plan's most fragile assumptions, breakpoints, and margin of safety. ## Core Features & Use Cases - Scenario Analysis: Re-runs the full three-statement model under coherent bundles of interrelated assumptions (e.g., downside = slower growth + price pressure + higher COGS + slower collections) and compares revenue, net income, operating cash flow, funding needed, runway, and covenant status. - Sensitivity & Fragility Ranking: Sweeps one variable at a time, computes output elasticity, and combines it with assumption confidence to rank the most-critical-and-most-uncertain drivers in tornado order. - Breakpoint & Margin-of-Safety Search: Solves for the exact value of each critical variable where the plan hits a funding gap, breaches a covenant, or runs out of cash, and quantifies how far the base assumption can move before failure. - Use Case: A founder asks "What if revenue growth is slower and competitors squeeze my prices?" The Skill re-runs the plan under a coherent downside, finds the growth rate at which funding needs exceed the revolver, flags a covenant breach, and recommends monitoring weekly bookings and average selling price. ## Quick Start Ask the AI to stress-test your base financial forecast with base, upside, and downside scenarios and identify which single assumption is most likely to break the plan.

Frequently Asked Questions about scenario-and-sensitivity-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stress-test a financial forecast with scenarios?▼

Define coherent Base, Upside, and Downside bundles where interrelated assumptions move together, then re-run the full three-statement model for each. Compare revenue, net income, operating cash flow, funding needed, runway, and covenant status across scenarios.

What is the difference between scenario analysis and sensitivity analysis?▼

Scenario analysis moves bundles of interrelated assumptions together to model realistic futures, while sensitivity analysis sweeps one variable at a time holding all else fixed. Scenarios show coherent outcomes; sensitivities isolate which single assumption the plan is most fragile to.

How do I find which assumption breaks my financial plan?▼

Run single-variable sweeps across each driver's plausible range and compute output elasticity, then combine it with assumption confidence into a fragility score. A breakpoint search solves for the exact value where funding gaps, covenant breaches, or cash-out occur.

When should I not use scenario and sensitivity analysis?▼

Do not use it before a base-case forecast exists; build one first with a forecast builder. Pure unit-economics questions belong to break-even and pricing analysis, and near-term cash-out risk belongs to a cash runway monitor.

Does scenario analysis require founder approval for mitigations?▼

Building scenarios, running sensitivities, and interpreting results never require approval. Arranging contingency financing, moving money, committing budget changes, or sharing sensitivity output externally always requires founder approval.