budget-planning
Skill1 starsChanged 7 months agoMITView on GitHub
Build departmental budgets with revenue forecasting, expense modeling, and scenario analysis. Use when building annual or quarterly budgets, modeling headcount plans, forecasting revenue by segment, or running best/base/worst case scenarios. Trigger with "build a budget", "annual plan", "expense forecast", "revenue model", "headcount plan", or "scenario analysis".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- t46/ra-skillstheir own version, first seen May 18, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- t46/ra-skills★ 16same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 165
Use fully loaded cost for people (salary + benefits + payroll taxes + equity + equipment), not just base salary.
- Distinctive: line 166
Always include a contingency or reserve line (typically 5-10% of discretionary spend).
- Distinctive: line 167
Test sensitivity on the 2-3 assumptions that matter most (usually revenue growth, churn, and hiring pace).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Budget Planning
Build departmental and company-level budgets: revenue forecasting, expense modeling, headcount planning, capital expenditure, and scenario analysis with sensitivity tables.
Workflow
Step 1: Define Budget Parameters
Establish the planning framework:
- Scope: Full company, specific department, project, or product line.
- Period: Fiscal year with monthly or quarterly granularity.
- Approach: Top-down (targets set by leadership), bottom-up (built from department inputs), zero-based (justify every dollar from scratch), or rolling (continuously updated).
- Currency: Functional currency; note FX assumptions for multi-currency operations.
- Key assumptions: Growth rates, inflation, headcount, pricing changes.
Step 2: Build the Revenue Budget
Model revenue by stream:
Subscription/Recurring Revenue:
- Beginning ARR/MRR.
- New bookings (volume x ACV by segment).
- Expansion revenue (upsell/cross-sell rate on installed base).
- Churn and contraction (historical rate applied to base).
- Ending ARR/MRR and recognized revenue by month.
Transactional/Product Revenue:
- Unit volume forecast (historical trend, pipeline, market sizing).
- Average selling price (with price increase assumptions).
- Seasonality adjustments by month.
Services/Professional Revenue:
- Billable headcount x utilization rate x billing rate.
- Project pipeline with expected start dates and durations.
Step 3: Build the Expense Budget
Model expenses by category:
People Costs (typically 60-80% of OpEx):
- Current headcount by department, role, and fully loaded cost.
- Planned hires: start date, ramp period, fully loaded cost (salary + benefits + taxes + equity).
- Merit increases (typically 3-5% annually, applied at review date).
- Attrition assumption (historical rate, typically 10-20%).
- Contractor and temp staffing.
Non-People Costs:
- Software and tools (per-seat or enterprise licenses).
- Cloud infrastructure (usage-based with growth factor).
- Facilities (rent, utilities, maintenance -- typically fixed).
- Travel and entertainment (per-head or per-trip basis).
- Professional services (legal, audit, consulting -- project-based).
- Marketing programs (by campaign or channel).
Capital Expenditure:
- Equipment and hardware purchases.
- Leasehold improvements.
- Capitalized software development.
Step 4: Run Scenario Analysis
Model three scenarios with different assumptions:
| Assumption | Downside | Base Case | Upside |
| Revenue growth | X% | Y% | Z% |
| New bookings | Low | Plan | Stretch |
| Churn rate | High | Historical | Improved |
| Headcount adds | Freeze | Plan | Accelerated |
| Cost inflation | High | Moderate | Low |
For each scenario, calculate: revenue, gross profit, operating income, cash flow, and runway.
Step 5: Consolidate and Present
Assemble the budget into a presentation-ready format.
Output Format
## Budget: [Scope] | [Period]
### Key Assumptions
| Assumption | Value | Basis |
|-------------------------|-------------|------------------------|
| Revenue growth rate | 25% | Pipeline + historical |
| Gross margin target | 65% | Pricing model |
| Net new hires | 15 FTEs | Dept plans |
| Attrition rate | 12% | Trailing 12-month avg |
| Merit increase | 4% | Market benchmark |
### Revenue Budget (Monthly)
| Month | Recurring | Transactional | Services | Total Revenue |
|---------|-----------|---------------|----------|---------------|
| Jan | $800K | $150K | $50K | $1,000K |
| Feb | $820K | $130K | $55K | $1,005K |
| ... | | | | |
| **FY** | **$10.5M**| **$1.8M** | **$700K**| **$13.0M** |
### Expense Budget by Department
| Department | People | Non-People | Total | % of Revenue |
|-------------|----------|------------|----------|-------------|
| Engineering | $3.2M | $800K | $4.0M | 30.8% |
| Sales & Mktg | $2.5M | $600K | $3.1M | 23.8% |
| G&A | $1.0M | $400K | $1.4M | 10.8% |
| **Total** | **$6.7M**| **$1.8M** | **$8.5M**| **65.4%** |
### Headcount Plan
| Department | Current | Q1 Adds | Q2 Adds | Q3 Adds | Q4 Adds | YE Target |
|-------------|---------|---------|---------|---------|---------|-----------|
| Engineering | 25 | 3 | 2 | 2 | 1 | 33 |
| Sales | 12 | 2 | 1 | 1 | 1 | 17 |
### Scenario Summary
| Metric | Downside | Base Case | Upside |
|--------------------|-----------|-----------|-----------|
| Revenue | $11.0M | $13.0M | $15.0M |
| Operating Income | ($500K) | $500K | $1.5M |
| Cash at Year End | $2.0M | $4.5M | $7.0M |
| Runway (months) | 18 | 30+ | 30+ |Examples
User: "Build the 2027 annual budget for the engineering department" Action: Model headcount (current + planned hires with start dates), compute fully loaded costs, add non-people costs (cloud, tools, travel), and present monthly with quarterly subtotals.
User: "Run a downside scenario if we miss revenue by 20%" Action: Apply a 20% revenue reduction, model the impact on gross profit, identify expense levers (hiring freeze, vendor cuts), and calculate revised cash runway.
User: "What's the headcount plan to support 30% growth?" Action: Model the required hires by department based on productivity ratios, calculate the cost impact, and phase hires across quarters.
Best Practices
- Build from the bottom up when possible; top-down targets without departmental input lack buy-in.
- Phase hires by start month, not quarter, to get accurate people cost timing.
- Include a ramp period for new hires (typically 3-6 months to full productivity).
- Model attrition explicitly; net headcount growth = gross hires minus attrition.
- Use fully loaded cost for people (salary + benefits + payroll taxes + equity + equipment), not just base salary.
- Always include a contingency or reserve line (typically 5-10% of discretionary spend).
- Test sensitivity on the 2-3 assumptions that matter most (usually revenue growth, churn, and hiring pace).
- Present scenarios as a range, not a single point estimate.
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.

