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

budget-vs-actuals-and-reforecast

Use when the user asks about budgets, pacing against plan, forecasts, re-forecasts, annual plans, or where a period lands at the current run rate.

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

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.3 KB

SKILL.md(원문)

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

Budget vs actuals and reforecast

Run this when the user wants to know where a period lands: pacing against plan, the forecast behind it, or a re-forecast after something moved. Read from the ledger only — anything untraceable is UNKNOWN, never estimated.

Inputs

The finance ledger, the budget set with one row per line and owner, and the period calendar.

Name the drivers before the dollars

Forecast driver-first: name the 5-15 drivers that actually move the plan — units times price, headcount times rate, pipeline times win rate — and give each one an owner in the assumption log. Model the drivers, then let the dollars follow. A plan built straight from last year plus a percentage is not a forecast.

Read every line against its plan

Per line: actuals to date, the share of the plan already used, days elapsed against days in the period, and where the period lands if the current run rate holds. Show the math, not just the verdict. Keep a rolling 12-18 month horizon — drop the expired month, add a new one at the end.

This is also the pace check the user can ask for at any point in the month: every budget line read at once, with month-to-date actuals and the landing point per line.

Flag both directions

Flag any line projected to pass its plan, and give the run rate it would take to land on plan instead. Flag any line pacing more than 15% under plan too — budget left on the table is a miss, not a saving. Every flag carries the gap in currency, the driver behind it, and one play with a named owner.

Grade the forecast

Base (commit), Adverse (downside), or Opportunity (upside), with one evidence line behind each grade. Base needs a named driver, not hope.

Re-forecast without re-baselining

Re-forecast monthly with a deeper refresh each quarter. On every re-forecast: restate the prior forecast, name what moved and by how much, and carry forward only the drivers still true. Never silently re-baseline. Track accuracy against the prior forecast — bias direction and miss size — and feed repeat misses back into the driver assumptions.

Reallocation asks

Move named money between lines with the total flat, cap any single move at 30% of the source line, and say which owner approved each move. Draft only — you never move a budget yourself.

Name the gaps

If a month or quarter is missing from the ledger, say which one and ask for that export. Do not smooth over the gap with a projection, and do not put a placeholder number where an actual belongs.

Output

One line per budget line, then the total, then the forecast grade and any reallocation draft. Under 200 words unless they asked for a table.

Fallbacks

No budget set: build the read against last period's actuals and label every plan number INFERENCE. No ledger at all: ask for one export and say exactly which columns you need.

Approval gate

Reads and drafts only. Budget moves, plan changes, and anything leaving the team wait for the owner's yes.

리뷰

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

댓글

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

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

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

0 / 1,000자

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

같은 저장소의 스킬

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

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

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

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

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

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

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Write ad variants that each test one idea, within platform limits and supported claims.

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

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

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

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

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

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Significant-Gravitas의 스킬 모두 보기

이 스킬의 문제 신고