mcpbeat Sign in

Budgeting And Forecasting Agent Skill

Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals against plan. Use this to build or challenge a budget, run a forecast cycle, consolidate departmental submissions, explain why results diverged from plan, or improve forecast accuracy.

673 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
220
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/cbrock84/headcount --skill budgeting-and-forecasting

The instruction itself

6 sections, as written by the author

Budgeting and forecasting

The budget is a commitment, the forecast is a belief

Keep them separate. A budget re-cut every month is not a commitment; a forecast held to the original

budget is not a belief. Both failures make the numbers useless for different reasons.

Running the cycle

  • Set the frame first — targets, headcount envelope, and the assumptions everyone builds on

(pricing, attrition, timing). Distributed teams building on different assumptions produces a

consolidation that cannot be reconciled.

  • Collect in a fixed template. Free-form submissions cost more to normalize than to build.
  • Challenge the inputs, specifically: what is the volume driver, what is this per unit, what

happens if it comes in at half. Budget submissions are negotiating positions and should be

treated as such without hostility.

  • Consolidate and find the gap between bottom-up and top-down. There always is one. Close it

explicitly by cutting something named, not by proportional trimming — proportional cuts damage

the highest-return line as much as the lowest.

  • Publish what was not funded and why. This prevents the same request arriving three times.

Rolling forecast

Re-forecast on a fixed cadence over a constant horizon. Update only what has changed and say what

changed and why. A re-forecast with no narrative is a new set of numbers with no information in it.

Variance analysis

Variance is only useful decomposed. For each material variance, separate:

  • Volume — did we do more or less of it?
  • Rate — did each unit cost or earn a different amount?
  • Timing — did it move between periods, or is it gone?
  • Mix — did the composition shift?

Timing variances need no action and are constantly mistaken for performance. Rate variances on

recurring costs compound and are constantly under-reacted to.

Explain the top few by value, not every line. A variance report covering everything gets read as

nothing.

Never

  • Present a forecast without saying what changed since the last one.
  • Let a department own an assumption that drives another department's numbers.
  • Report accuracy without measuring it. Track forecast error over time — it improves quickly once

visible and never improves while unmeasured.

How to use it

Copy the folder

Take cbrock84/budgeting-and-forecasting from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.