본문으로 건너뛰기
cccskills
무료GitHub에 공개

budgeting-and-forecasting

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(2)

  • SKILL.md3.4 KB
  • references/sources.md937 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

  1. 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.
  2. Collect in a fixed template. Free-form submissions cost more to normalize than to build.
  3. 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.
  4. 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.
  5. 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.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Tooling

Planning: Anaplan, Pigment, Workday Adaptive Planning, Vena, Cube, and similar. A well-built spreadsheet on a clean chart of accounts beats a planning tool nobody has been staffed to maintain; move when budget owners outnumber the people who can hold the model in their head.

Driver data comes from the ledger, the CRM, and the HRIS. The planning tool is only ever as current as those connections.

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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

cbrock84의 스킬 모두 보기

이 스킬의 문제 신고