project-budget
Skill0 starsChanged yesterdayMITView on GitHub
Build and track a project budget: cost lines from the task list, real quotes instead of guesses, a contingency reserve, the timing of payments, and a simple tracker of planned versus actual spending, ready to paste into a spreadsheet. Use for any project with money involved (renovation, event, wedding, move, equipment, IT project), when someone asks "how much will it cost?" or when costs start to slip. Triggers: "budget", "how much will it cost", "cost estimate", "track expenses", "budget du projet", "combien ça va coûter", "estimation des coûts", "suivi des dépenses", "presupuesto", "cuánto va a costar", "control de gastos".
In this repository15 other files it gives its agents.
- decision-makingSkill
- delegation-briefSkill
- meeting-toolkitSkill
- project-charterSkill
- project-recoverySkill
- project-scheduleSkill
- responsibility-matrixSkill
- retrospectiveSkill
- risk-registerSkill
- scope-changeSkill
- stakeholder-mapSkill
- status-updateSkill
- vendor-selectionSkill
- weekly-reviewSkill
- work-breakdownSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
After work-breakdown, before committing money.
- Very specific: line 22
When collecting quotes (vendor-selection compares them).
- Distinctive: line 23
When spending starts to drift from the plan.
- Distinctive: line 56
Every line shows where its price comes from and the date.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Project budget
Budgets go wrong in two ways: forgotten costs and optimistic guesses. This skill builds the budget from the task list, replaces guesses with quotes, sets a reserve, and tracks the real spending as the project goes.
When to use
- After
work-breakdown, before committing money. - When collecting quotes (
vendor-selectioncompares them). - When spending starts to drift from the plan.
Inputs
- The task list and deliverables.
- Quotes, price lists, receipts already available.
- The budget limit and how the project is paid for (savings, loan, company budget, grant).
Method
- List the cost lines from the deliverables: materials, labor and services, fees and permits, equipment, travel, insurance, taxes, and the costs people forget (delivery, waste removal, cleaning, temporary housing, training, subscriptions).
- Price each line from a source: a quote, a catalog price, a past invoice. Mark guesses as estimates and replace them with quotes before committing. Prices change: note the date of each price.
- Add a contingency reserve, sized to the uncertainty of the project, and say where the figure comes from. Large projects overrun often, as Flyvbjerg and Gardner document, so a reserve is planning, not pessimism.
- Plan the timing of payments: deposits, installments, final payments, and when the money must be available.
- Set up the tracker: planned, committed (signed but not paid), paid, and the remaining forecast for each line.
- Review it at each milestone: explain every gap, decide whether to use the reserve, cut scope (
scope-change) or find more money.
Output
### Budget: <project> (version <n>, <date>)
| Line | Source of the price (quote, date) | Planned | Committed | Paid | Forecast | Gap |
|---|---|---|---|---|---|---|
| Contingency reserve | … | | | | | |
| Total | | | | | | |
### Payment calendar
| Date | What | Amount | Paid from |
|---|---|---|---|Quality bar
- Every line shows where its price comes from and the date; guesses are labeled.
- The reserve is explicit and justified, never hidden inside the lines.
- The tracker separates planned, committed and paid.
- Taxes, fees and rules come from official sources with the date when they matter.
- Written in the user's language, with the terms below.
Terminology
| English | Français | Español |
| Budget | Budget | Presupuesto |
| Quote | Devis | Presupuesto (de un proveedor) |
| Contingency reserve | Provision pour imprévus | Reserva para imprevistos |
| Committed cost | Coût engagé | Coste comprometido |
| Cost overrun | Dépassement de budget | Sobrecoste |
| Payment schedule | Échéancier de paiement | Calendario de pagos |
Sources
- Flyvbjerg, B., & Gardner, D. (2023). How Big Things Get Done. Currency.
- Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK Guide) (7th ed.). Project Management Institute.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

