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

ops-capacity-and-headcount-plan

Use when the user asks whether staffing covers demand across the business, names a hiring target, or hands over workload and team numbers: company-wide headcount planning with scenarios, not support shift scheduling.

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

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md2.9 KB

SKILL.md(원문)

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

Plan capacity and headcount

Use this when the user asks whether staffing covers demand, names a hiring target, or hands over workload and team numbers. This is the business-wide plan — demand per function, required heads, the hiring plan, and the scenarios. Interval-level contact forecasting, shift schedules, and intra-day moves for a support desk belong to the workforce planning skill, not here.

What you need first

Past demand by function and period, current heads and roles, shrinkage drivers (time off, training, attrition), open requisitions, and the forecast horizon.

No demand history means a judgment forecast marked INFERENCE with the data need named. No shrinkage figure means you plan at 20% and say so.

Forecast demand per role, skill, and level

Forecast from history, never from headcount totals alone. Name the trend, the seasonality, and the known events — launches, renewals, holidays. Include pipeline-weighted demand, tentative work, and time off. State the horizon and the miss band plainly.

The 12-to-16-week horizon is what drives the hire, contract, or reskill call.

Turn the forecast into required heads

Required heads = base workload heads / (1 - shrinkage/100), where shrinkage covers time off, training, and attrition.

Show the math in one block so the capacity owner can check it. Call out the convention when overtime or contractors fill the gap instead of heads.

Gap it against today

Heads on hand, open requisitions with start dates, and the shortfall per function and month. Name coverage gaps, never hide them.

Scenario-plan two cases

Base and high demand. Each carries hiring targets, start-by dates, cost per hire beyond salary (benefits, onboarding time, tools, and time to full productivity), and what breaks if hires slip a month.

Before opening any role externally, check whether an existing team member can step in. Hold a per-function skills inventory beside the plan: current skills against required, the top two gaps, and whether each gap closes by hire, train, or contractor. Name every single-point-of-failure role.

Track monthly

Forecast against actual demand, hires landed against plan, utilization, and the one planning fix for next month. Log the forecast and the hires made.

Rules

Never present a guessed headcount as modeled. Never move requisition dates or headcount budgets without the capacity owner's yes.

Save the capacity plan under capacity, dated, with its scenarios.

리뷰

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

댓글

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

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

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. 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의 스킬 모두 보기

이 스킬의 문제 신고