← Power BI DesktopCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Power BI Desktop
Snapshot Sep 30, 2026 · 23:15 UTC · version 3.0.0+codex.20260829143201
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when calculating what must happen to reach Power BI revenue, budget, roll, margin, cash, or service targets, including reverse planning, target-gap decomposition, required backlog conversion, and required demand uplift.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 137
}
],
"name": "powerbi-goal-seeking-planning",
"skill_md_contents": "---\r\nname: powerbi-goal-seeking-planning\r\ndescription: Use when calculating what must happen to reach Power BI revenue, budget, roll, margin, cash, or service targets, including reverse planning, target-gap decomposition, required backlog conversion, and required demand uplift.\r\n---\r\n\r\n# Power BI Goal-Seeking Planning\r\n\r\nUse this skill when the question is \"What must happen to hit the target?\" rather than \"What will happen?\"\r\n\r\n## Workflow\r\n\r\n1. Select target: budget, roll forecast, prior year, management target, margin, or cash.\r\n2. Calculate current plan gap by month.\r\n3. Decompose the required change:\r\n - actual-to-date contribution\r\n - expected backlog conversion\r\n - residual demand required\r\n - customer/product gap drivers\r\n4. Rank feasible levers:\r\n - improve conversion\r\n - pull forward backlog\r\n - recover customer demand\r\n - substitute product/customer demand\r\n - challenge the target if infeasible\r\n5. Label target feasibility:\r\n - `achievable`\r\n - `stretch`\r\n - `unlikely`\r\n - `not_supported_by_data`\r\n\r\n## Required outputs\r\n\r\n- `forecast_month`\r\n- `target_name`\r\n- `target_value`\r\n- `current_forecast`\r\n- `target_gap`\r\n- `required_backlog_conversion`\r\n- `required_residual_demand`\r\n- `top_required_segments`\r\n- `feasibility`\r\n- `explanation`\r\n\r\n## Guardrails\r\n\r\n- Do not treat target closure as evidence that the target is realistic.\r\n- Separate mathematically required revenue from operationally feasible revenue.\r\n"
}SHA-256 of public snapshot: 396173877bc300e12367c6bfe1e4100823933bd56d21e094168f68b334101ee1