菜单
Use when adding causal and counterfactual thinking to Power BI sales forecasts, including working days, holidays, delivery constraints, price changes, product lifecycle, stockouts, campaigns, customer behavior, and best/base/worst case simulations.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when working with Microsoft Power BI Desktop files or projects, including PBIX/PBIT inventory, DAX and Power Query review, semantic model documentation, Tabular Editor workflows, and local Desktop environment checks.
Use when storing and reusing Power BI planning memory across cycles, including forecast versions, assumptions, actions, overrides, actuals, error causes, segment lessons, and durable learning signals for autonomous planning.
Use when coordinating multiple AI forecasting perspectives for Power BI sales forecasts, including backlog, seasonality, budget, sales skepticism, risk, consensus, dissent, and explainable forecast arbitration.
Use when turning autonomous Power BI planning deviations into managed exceptions, including revenue gaps, risky backlog, unrealistic targets, biased models, sparse segments, owner hints, status, escalation, and closure evidence.
Use when building or running a closed-loop autonomous Power BI planning cycle that refreshes actuals, forecast, gap detection, scenarios, actions, tracking, learning, and the next plan without changing PBIX files directly.
Use when constraining Power BI revenue planning by delivery, capacity, stock, supply, margin, cash, payment terms, sales resources, or operational feasibility rather than forecasting unconstrained demand only.
| name | powerbi-causal-counterfactual-forecasting |
| description | Use when adding causal and counterfactual thinking to Power BI sales forecasts, including working days, holidays, delivery constraints, price changes, product lifecycle, stockouts, campaigns, customer behavior, and best/base/worst case simulations. |
Use this skill when the user asks why a forecast changes, what causes a revenue gap, or what would happen under alternative assumptions.
forecast_monthdriverdriver_typebase_valuecounterfactual_valuerevenue_impactconfidenceevidenceactionabilityhypothesis when the data only supports association.