team-budget-tracker
Track a team's budget so surprises die young — the commitment-based view (spent + committed + planned, not just invoiced), the category grain that matches how the team actually spends, the monthly close with its one-sentence read, and the forecast honesty for the year-end question. Use when asked track my team's budget, are we going to blow the budget, why did finance's number surprise us, or set up budget visibility for the team. Produces the three-lane tracker (spent/committed/planned), the monthly close ritual, the variance signals, and the year-end forecast method.
npx skills add mohitagw15856/pm-claude-skills --skill team-budget-tracker --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Team Budget Tracker Skill Team budgets surprise their owners for one structural reason: the official number tracks *invoices* (what finance has processed), while the truth includes *commitments* (the signed contract not yet billed, the accepted quote, the hire with an offer out) — so a team can be "under budget" while being catastrophically over-committed. The tracker runs three lanes — **spent** (invoiced), **committed** (contractually owed), **planned** (intended but not yet signed) — against the budget line, at the [budget-tracker-design](../budget-tracker-design/SKILL.md) statement-grain, with the monthly close and its one-sentence read. The remaining-to-spend number the team actually needs is budget − spent − committed, and most surprise stories are the word "committed" going untracked. ## What This Skill Produces - **The three-lane tracker** — spent / committed / planned per category, with true-remaining computed - **The commitment intake** — the rule that signatures, POs, and offers enter the tracker at commitment-time ([contract-renewal-tracker](../contract-renewal-tracker/SKILL.md) intake logic, budget edition) - **The monthly close** — reconcile with finance's actuals,
- What This Skill Produces
- Required Inputs
- Framework: The Tracker Rules
- Output Format
- The Three Lanes
- Commitment Intake
- The Monthly Close ([date])
- The Forecast
- Quality Checks
- Anti-Patterns
What does the team-budget-tracker skill do?
Track a team's budget so surprises die young — the commitment-based view (spent + committed + planned, not just invoiced), the category grain that matches how the team actually spends, the monthly close with its one-sentence read, and the forecast honesty for the year-end question. Use when asked track my team's budget, are we going to blow the budget, why did finance's number surprise us, or set up budget visibility for the team. Produces the three-lane tracker (spent/committed/planned), the monthly close ritual, the variance signals, and the year-end forecast method.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill team-budget-tracker --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
