[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F7BP4PP3KTDA6R1F9HH4PS":3,"skill-same:01M7F7BP4PP3KTDA6R1F9HH4PS":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":14,"repositoryHtmlUrl":45,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M7F7BP4PP3KTDA6R1F9HH4PS","conducting-scenario-planning",null,"Structures financial scenario analysis with assumption modeling, sensitivity testing, and decision frameworks. Use when modeling scenarios, testing assumptions, or evaluating strategic options.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fconducting-scenario-planning\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: conducting-scenario-planning\nlanguage: en\ndescription: Structures financial scenario analysis with assumption modeling, sensitivity testing, and decision frameworks. Use when modeling scenarios, testing assumptions, or evaluating strategic options.\ntags:\n  - process\n  - financial-planning-and-analysis\nmetadata:\n  author: casemark\n  practice_areas:\n    - FP&A\n    - Management Accounting\n    - Business Intelligence\n  document_types:\n    - Process Documentation\n  skill_modes:\n    - Process Management\nsource: \"https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills\"\nsource_repository: \"CaseMark\u002Fskills\"\nsource_path: \"skills\u002Ffinance\u002Fconducting-scenario-planning\u002FSKILL.md\"\nlicense: \"Apache-2.0\"\nimported_at: \"2026-09-20\"\n---\n# Conducting Scenario Planning\n\nStructures financial scenario analysis with assumption modeling, sensitivity testing, and decision frameworks for strategic and operational planning.\n\n## When To Use\n\n- Annual or quarterly budgeting cycles requiring upside\u002Fdownside forecasts\n- Evaluating capital allocation decisions (M&A, capex, new product lines)\n- Stress-testing a business plan against macro or market disruptions\n- Board or leadership presentations that need a range of financial outcomes\n- Assessing go\u002Fno-go thresholds for strategic initiatives\n- Contingency planning for supply chain, pricing, or demand shocks\n\n## Inputs To Gather\n\n- **Baseline financial model** — P&L, cash flow, and balance sheet projections with current assumptions\n- **Key assumption variables** — the 5–10 drivers with the highest impact on outcomes (e.g., revenue growth rate, COGS %, customer churn, FX rates, interest rates)\n- **Historical ranges** — actual min\u002Fmax\u002Fmean values for each variable over a relevant lookback period (typically 3–5 years)\n- **External benchmarks** — industry comps, analyst consensus, or macro forecasts that bound plausible ranges\n- **Management hypotheses** — specific strategic actions or events to model (e.g., price increase, market entry, headcount freeze)\n- **Decision criteria** — the metrics stakeholders will use to choose between scenarios (e.g., EBITDA margin, FCF breakeven, covenant compliance, IRR hurdle)\n\n## Workflow\n\n1. **Define scenario architecture**\n   - Select the scenario framework: discrete scenarios (base\u002Fbull\u002Fbear), Monte Carlo simulation, or combinatorial matrix\n   - For discrete scenarios, name and narratively define each case (e.g., \"Bear: recession + 15% volume decline + 200bps rate increase\")\n   - Identify which variables shift between scenarios and which remain constant\n\n2. **Set assumption ranges**\n   - For each key variable, assign a value per scenario or a probability distribution\n   - Document the source and rationale for every assumption (historical data, management estimate, third-party forecast)\n   - Flag any assumption lacking empirical support with [VERIFY]\n\n3. **Build scenario outputs**\n   - Run each scenario through the financial model to produce projected P&L, cash flow, and balance sheet\n   - Calculate decision-relevant metrics: revenue, EBITDA, net income, FCF, leverage ratios, liquidity runway, ROI\u002FIRR\n   - Capture the delta vs. baseline for each metric to highlight scenario impact\n\n4. **Perform sensitivity analysis**\n   - Isolate individual variables via one-at-a-time sensitivity (tornado chart)\n   - Identify breakeven thresholds — the variable value at which a key metric crosses a critical boundary (e.g., \"revenue must exceed $X for covenant compliance\")\n   - Run two-way sensitivity tables for the top correlated variable pairs\n\n5. **Assess probability and risk**\n   - Assign subjective or data-driven probability weights to each scenario if stakeholders require an expected-value view\n   - Map scenarios to a risk matrix (likelihood × financial impact)\n   - Identify tail-risk scenarios that, while low-probability, would be existential or covenant-breaking\n\n6. **Develop decision framework**\n   - Link each scenario outcome to a recommended action or contingency trigger\n   - Define early-warning indicators that signal which scenario is materializing (e.g., \"if Q1 bookings fall below $Y, activate cost-reduction playbook\")\n   - Present a decision table: scenario → metric outcome → recommended action → trigger\u002Ftimeline\n\n7. **Document and present**\n   - Summarize findings in an executive brief: key takeaways, scenario comparison table, sensitivity highlights, and recommended path\n   - Include an appendix with full assumption tables, model outputs, and methodology notes\n   - Clearly separate facts, assumptions, and recommendations throughout\n\n## Output\n\n- **Scenario summary table** — side-by-side comparison of 3–5 scenarios across all decision metrics\n- **Sensitivity analysis exhibits** — tornado chart ranking variable impact; two-way tables for top pairs; breakeven thresholds\n- **Decision matrix** — scenario-to-action mapping with triggers and timelines\n- **Assumption register** — complete list of every variable, its value per scenario, source, and confidence level\n- **Executive narrative** — 1–2 page summary suitable for board or leadership review\n\n## Quality Checks\n\n- Every assumption has a documented source; unsupported assumptions are tagged [VERIFY]\n- Scenario definitions are mutually distinct and collectively span a realistic range — no two scenarios overlap excessively\n- Model mechanics are validated: baseline scenario ties back to the approved budget or latest forecast within acceptable tolerance [VERIFY against current approved numbers]\n- Sensitivity analysis covers all variables identified as high-impact; no material driver is omitted\n- Decision triggers are specific and measurable, not vague (\"monitor closely\")\n- Outputs are stress-tested for internal consistency — e.g., cash flow aligns with P&L and balance sheet movements\n- Tax rates, depreciation schedules, and working capital assumptions are jurisdiction-appropriate [VERIFY]\n- Presentation distinguishes clearly between deterministic outputs and probability-weighted expected values\n","# Conducting Scenario Planning\n\nStructures financial scenario analysis with assumption modeling, sensitivity testing, and decision frameworks for strategic and operational planning.\n\n## When To Use\n\n- Annual or quarterly budgeting cycles requiring upside\u002Fdownside forecasts\n- Evaluating capital allocation decisions (M&A, capex, new product lines)\n- Stress-testing a business plan against macro or market disruptions\n- Board or leadership presentations that need a range of financial outcomes\n- Assessing go\u002Fno-go thresholds for strategic initiatives\n- Contingency planning for supply chain, pricing, or demand shocks\n\n## Inputs To Gather\n\n- **Baseline financial model** — P&L, cash flow, and balance sheet projections with current assumptions\n- **Key assumption variables** — the 5–10 drivers with the highest impact on outcomes (e.g., revenue growth rate, COGS %, customer churn, FX rates, interest rates)\n- **Historical ranges** — actual min\u002Fmax\u002Fmean values for each variable over a relevant lookback period (typically 3–5 years)\n- **External benchmarks** — industry comps, analyst consensus, or macro forecasts that bound plausible ranges\n- **Management hypotheses** — specific strategic actions or events to model (e.g., price increase, market entry, headcount freeze)\n- **Decision criteria** — the metrics stakeholders will use to choose between scenarios (e.g., EBITDA margin, FCF breakeven, covenant compliance, IRR hurdle)\n\n## Workflow\n\n1. **Define scenario architecture**\n   - Select the scenario framework: discrete scenarios (base\u002Fbull\u002Fbear), Monte Carlo simulation, or combinatorial matrix\n   - For discrete scenarios, name and narratively define each case (e.g., \"Bear: recession + 15% volume decline + 200bps rate increase\")\n   - Identify which variables shift between scenarios and which remain constant\n\n2. **Set assumption ranges**\n   - For each key variable, assign a value per scenario or a probability distribution\n   - Document the source and rationale for every assumption (historical data, management estimate, third-party forecast)\n   - Flag any assumption lacking empirical support with [VERIFY]\n\n3. **Build scenario outputs**\n   - Run each scenario through the financial model to produce projected P&L, cash flow, and balance sheet\n   - Calculate decision-relevant metrics: revenue, EBITDA, net income, FCF, leverage ratios, liquidity runway, ROI\u002FIRR\n   - Capture the delta vs. baseline for each metric to highlight scenario impact\n\n4. **Perform sensitivity analysis**\n   - Isolate individual variables via one-at-a-time sensitivity (tornado chart)\n   - Identify breakeven thresholds — the variable value at which a key metric crosses a critical boundary (e.g., \"revenue must exceed $X for covenant compliance\")\n   - Run two-way sensitivity tables for the top correlated variable pairs\n\n5. **Assess probability and risk**\n   - Assign subjective or data-driven probability weights to each scenario if stakeholders require an expected-value view\n   - Map scenarios to a risk matrix (likelihood × financial impact)\n   - Identify tail-risk scenarios that, while low-probability, would be existential or covenant-breaking\n\n6. **Develop decision framework**\n   - Link each scenario outcome to a recommended action or contingency trigger\n   - Define early-warning indicators that signal which scenario is materializing (e.g., \"if Q1 bookings fall below $Y, activate cost-reduction playbook\")\n   - Present a decision table: scenario → metric outcome → recommended action → trigger\u002Ftimeline\n\n7. **Document and present**\n   - Summarize findings in an executive brief: key takeaways, scenario comparison table, sensitivity highlights, and recommended path\n   - Include an appendix with full assumption tables, model outputs, and methodology notes\n   - Clearly separate facts, assumptions, and recommendations throughout\n\n## Output\n\n- **Scenario summary table** — side-by-side comparison of 3–5 scenarios across all decision metrics\n- **Sensitivity analysis exhibits** — tornado chart ranking variable impact; two-way tables for top pairs; breakeven thresholds\n- **Decision matrix** — scenario-to-action mapping with triggers and timelines\n- **Assumption register** — complete list of every variable, its value per scenario, source, and confidence level\n- **Executive narrative** — 1–2 page summary suitable for board or leadership review\n\n## Quality Checks\n\n- Every assumption has a documented source; unsupported assumptions are tagged [VERIFY]\n- Scenario definitions are mutually distinct and collectively span a realistic range — no two scenarios overlap excessively\n- Model mechanics are validated: baseline scenario ties back to the approved budget or latest forecast within acceptable tolerance [VERIFY against current approved numbers]\n- Sensitivity analysis covers all variables identified as high-impact; no material driver is omitted\n- Decision triggers are specific and measurable, not vague (\"monitor closely\")\n- Outputs are stress-tested for internal consistency — e.g., cash flow aligns with P&L and balance sheet movements\n- Tax rates, depreciation schedules, and working capital assumptions are jurisdiction-appropriate [VERIFY]\n- Presentation distinguishes clearly between deterministic outputs and probability-weighted expected values\n",{"name":5,"tags":24,"source":27,"license":15,"language":28,"metadata":29,"description":7,"imported_at":39,"source_path":40,"source_repository":41},[25,26],"process","financial-planning-and-analysis","https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills","en",{"author":30,"skill_modes":31,"document_types":33,"practice_areas":35},"casemark",[32],"Process Management",[34],"Process Documentation",[36,37,38],"FP&A","Management Accounting","Business Intelligence","2026-09-20","skills\u002Ffinance\u002Fconducting-scenario-planning\u002FSKILL.md","CaseMark\u002Fskills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Ffinance\u002Fconducting-scenario-planning","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill conducting-scenario-planning",{"tool":54,"command":55},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill conducting-scenario-planning",{"tool":57,"command":58},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill conducting-scenario-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fconducting-scenario-planning\u002FSKILL.md",true,[],[63,71,78,85,92,99],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]