Agent skill

Workforce Planning

by cbrock84 in cbrock84/headcount

Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget.

MITAuto-check passedBusiness, Finance & HR

Install Workforce Planning

skills CLI
$ npx skills add cbrock84/headcount --skill workforce-planning -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cbrock84/headcount workforce-planning --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/people/skills/workforce-planning .claude/skills/workforce-planning && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
workforce-planning
GitHub stars
2k
Token cost
~817 tokens
SKILL.md length
460 words
Files
2 (incl. references)
Skills in repo
175
Repo updated
First seen
Licence
MIT

At a glance

Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget.

  • Business, Finance & HR work in your project
  • SKILL.md covers Plan capability, not headcount, Sequence matters more than total, Attrition is a planning input and Scenarios, including down, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Workforce Planning is an agent skill from cbrock84/headcount. Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget. Use this to build a hiring plan, decide which roles to open and in what order, model attrition and backfill, plan for a growth or contraction scenario, or connect headcount plans to the budget.

Its SKILL.md is about 820 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).

It sits in Business, Finance & HR. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.

When your agent uses it

  • Business, Finance & HR work in your project

Example prompts

  • “Use the workforce-planning skill to plan the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring…”
  • “/workforce-planning”

What it can do on your machine

Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Workforce Planning loads about 817 tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 85 tokens; SKILL.md has 460 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~85
When it runs · the whole SKILL.md, loaded when a task matches
~817
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 460 words, ~817 tokens.

Download SKILL.mdSave it as .claude/skills/workforce-planning/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
workforce-planning
description
Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget. Use this to build a hiring plan, decide which roles to open and in what order, model attrition and backfill, plan for a growth or contraction scenario, or connect headcount plans to the budget.

Workforce planning

A hiring plan is an org design decision spread over twelve months and a large financial commitment made in small pieces. It deserves the scrutiny of both.

Plan capability, not headcount

Headcount is an input. Start from what the organization must be able to do that it currently cannot, then work out what closes the gap — hiring, developing existing people, contracting, or not doing the work.

The shape follows from people:org-design; this is about sequencing and quantity over time, funded against finance:budgeting-and-forecasting on fully loaded cost rather than salary. Salary is typically well under the true cost, and plans built on it are wrong by a wide and consistent margin.

Sequence matters more than total

Twelve hires in a year is not one number; it is twelve dated decisions with dependencies.

  • Hire the people who make other hires productive first. A manager, a lead, or the person who can onboard the next five. Hiring five juniors before the person who will develop them wastes most of the investment.
  • Respect absorption capacity. An organization can only integrate so many people at once before onboarding quality falls and existing output drops. Growth past that rate makes things slower for a quarter, reliably.
  • Front-load long-lead roles. Scarce skills take months to find. Plotting them at the same lead time as abundant ones is how plans silently slip.

Attrition is a planning input

Some attrition is expected and healthy; the planning error is treating it as noise. Model it by segment — teams, levels and tenure bands differ substantially — and plan backfill lead time from the resignation date, not the leaving date.

Watch regretted attrition specifically, and by manager. Aggregate attrition looks fine while one team is bleeding people, and the aggregate is what gets reported.

Show full SKILL.md (167 more words)Show less

Scenarios, including down

Plan the base case, the growth case and the contraction case. Knowing in advance what you would stop doing, and which commitments are hard to reverse, is what makes a downturn a decision rather than a scramble.

Offers, notice periods and some contractor arrangements are commitments before anyone starts. Know which parts of the plan can still be unwound and by when.

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.

Never

  • Build a plan on salary rather than fully loaded cost.
  • Hire faster than the organization can absorb and expect output to rise.
  • Treat attrition as a residual instead of a modeled input.
  • Report aggregate attrition without looking at it by team and by manager.

© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/people/skills/workforce-planning of cbrock84/headcount.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Workforce Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Workforce Planning compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workforce Planning this skillcbrock84/headcount2k—~817Automated safety check: PassMIT
Technical Analysttradermonty/claude-trading-skills3k5 repos~4.6kAutomated safety check: PassMIT
Creating Financial ModelsChen-zexi/open-ptc-agent7294 repos~1.3kAutomated safety check: PassMIT
Stock APIzhangxiangliang/stock-api2k—~507Automated safety check: PassMIT
Theme Detectortradermonty/claude-trading-skills3k2 repos~4.9kAutomated safety check: PassMIT
Itr Walakaranb192/itr-wala871—~3.6kAutomated safety check: PassMIT

Similar skills

  • Technical Analyst

    tradermonty/claude-trading-skills

    This skill should be used when analyzing weekly price charts for stocks, stock indices, cryptocurrencies, or forex pairs.

    3k GitHub starsUsed in 5 repos~4.6k tokens
    Business, Finance & HRAuto-check passed
  • Creating Financial Models

    Chen-zexi/open-ptc-agent

    This skill provides an advanced financial modeling suite with DCF analysis, sensitivity testing, Monte Carlo simulations, and scenario planning for investment decisions

    729 GitHub starsUsed in 4 repos~1.3k tokens
    Business, Finance & HRAuto-check passed
  • Stock API

    zhangxiangliang/stock-api

    Fetch real-time stock quotes, K-line (candlestick) history, and search symbols for China A-shares, Hong Kong, and US markets.

    2k GitHub stars~507 tokensUpdated today
    Business, Finance & HRAuto-check passed
  • Theme Detector

    tradermonty/claude-trading-skills

    Detect and analyze trending market themes across sectors. An agent skill from tradermonty/claude-trading-skills.

    3k GitHub starsUsed in 2 repos~4.9k tokens
    Business, Finance & HRAuto-check passed
  • Itr Wala

    karanb192/itr-wala

    File Indian income tax returns (ITR) for FY 2025-26 / AY 2026-27.

    871 GitHub stars~3.6k tokensUpdated 4 days ago
    Business, Finance & HRAuto-check passed
  • Tushare Data

    zillionare/zillionare

    面向中文自然语言的 Tushare 数据研究技能。用于把“看看这只股票最近怎么样”“帮我查财报趋势”“最近哪个板块最强”“北向资金在买什么”“给我导出一份行情数据”这类请求,转成可执行的数据获取、清洗、对比、筛选、导出与简要分析流程。适用于 A 股、指数、ETF/基金、财务、估值、资金流、公告新闻、板块概念与宏观数据等研究场景。

    319 GitHub starsUsed in 2 repos~2.3k tokens
    Business, Finance & HRAuto-check passed

More from cbrock84/headcount

All 175 skills in this repo
  • Agent Hierarchy

    cbrock84/headcount

    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…

    2k GitHub stars~1.2k tokensUpdated 21 days ago
    Auto-check passed
  • Access And Identity

    cbrock84/headcount

    Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.

    2k GitHub stars~1.1k tokensUpdated 21 days ago
    Auto-check passed
  • Account Based Marketing

    cbrock84/headcount

    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…

    2k GitHub stars~1.2k tokensUpdated 21 days ago
    Auto-check passed
  • Activation

    cbrock84/headcount

    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.

    2k GitHub stars~865 tokensUpdated 21 days ago
    Auto-check passed
  • AI Research Analyst

    cbrock84/headcount

    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.

    2k GitHub stars~916 tokensUpdated 21 days ago
    Auto-check passed
  • AI Search Optimization

    cbrock84/headcount

    Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf.

    2k GitHub stars~829 tokensUpdated 21 days ago
    Auto-check passed

Questions about Workforce Planning

What does Workforce Planning do?

Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget. Workforce Planning is an agent skill from cbrock84/headcount. Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget.

When should I use Workforce Planning?

Workforce Planning fits situations like: business, Finance & HR work in your project.

How do I install Workforce Planning in Claude Code?

Run `npx skills add cbrock84/headcount --skill workforce-planning -a claude-code`. Or copy the skill folder (plugins/people/skills/workforce-planning in cbrock84/headcount) into .claude/skills/workforce-planning in your project. Claude Code loads it when a task matches its description.

How do I install Workforce Planning in Codex?

Run `npx skills add cbrock84/headcount --skill workforce-planning -a codex`. Or copy the skill folder (plugins/people/skills/workforce-planning in cbrock84/headcount) into .agents/skills/workforce-planning in your project. Codex loads it when a task matches its description.

Can I use Workforce Planning in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill workforce-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workforce-planning, .gemini/skills/workforce-planning, .github/skills/workforce-planning and .opencode/skills/workforce-planning in your project.

What does Workforce Planning need to run?

SKILL.md names no scripts, command-line tools or credentials: Workforce Planning is instructions for the agent only.

Does Workforce Planning access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Workforce Planning safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Workforce Planning use?

Workforce Planning is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workforce Planning use?

About 817 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 324 tokens, read only when the agent opens those files.

What are the alternatives to Workforce Planning?

Skills that share tags, products or a category with Workforce Planning: Technical Analyst (tradermonty/claude-trading-skills, 3k stars), Creating Financial Models (Chen-zexi/open-ptc-agent, 729 stars), Stock API (zhangxiangliang/stock-api, 2k stars) and Theme Detector (tradermonty/claude-trading-skills, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workforce Planning?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,007 GitHub stars. The repository holds 175 skills in this directory. The repository was last updated on September 17, 2026.

Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.