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.
npx skills add https://github.com/cbrock84/headcount --skill budgeting-and-forecasting
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.
(pricing, attrition, timing). Distributed teams building on different assumptions produces a
consolidation that cannot be reconciled.
happens if it comes in at half. Budget submissions are negotiating positions and should be
treated as such without hostility.
explicitly by cutting something named, not by proportional trimming — proportional cuts damage
the highest-return line as much as the lowest.
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 is only useful decomposed. For each material variance, separate:
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.
visible and never improves while unmeasured.
Take cbrock84/budgeting-and-forecasting from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.