Agent skill

Capacity And Demand Planning

by cbrock84 in cbrock84/headcount

Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity.

MITAuto-check passedData & Analytics

Install Capacity And Demand Planning

skills CLI
$ npx skills add cbrock84/headcount --skill capacity-and-demand-planning -a claude-code

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

GitHub CLI
$ gh skill install cbrock84/headcount capacity-and-demand-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/operations/skills/capacity-and-demand-planning .claude/skills/capacity-and-demand-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
capacity-and-demand-planning
GitHub stars
2k
Token cost
~814 tokens
SKILL.md length
436 words
Files
2 (incl. references)
Skills in repo
178
Repo updated
First seen
Licence
MIT

At a glance

Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity.

  • Tasks that involve Forecasting and time series
  • SKILL.md covers Forecast demand honestly, Capacity is not headcount, Queues tell you before the… and Add capacity or fix flow, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Capacity And Demand Planning is an agent skill from cbrock84/headcount. Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity. Use this to plan staffing for expected volume, diagnose a queue that keeps growing, size support or fulfillment capacity, or decide whether a bottleneck needs more capacity or better flow.

Its SKILL.md is about 810 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 Data & Analytics, covering Forecasting and time series. 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

  • Tasks that involve Forecasting and time series

Example prompts

  • “Use the capacity-and-demand-planning skill to match operational capacity to expected demand — forecasting load, sizing teams and systems, managing…”
  • “/capacity-and-demand-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

Capacity And Demand Planning loads about 814 tokens when it runs, and up to ~1k if it reads all its reference files. Until then it costs about 91 tokens; SKILL.md has 436 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~91
When it runs · the whole SKILL.md, loaded when a task matches
~814
With references · SKILL.md plus every file in references/, read only if the agent opens them
~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). 436 words, ~814 tokens.

Download SKILL.mdSave it as .claude/skills/capacity-and-demand-planning/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
capacity-and-demand-planning
description
Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity. Use this to plan staffing for expected volume, diagnose a queue that keeps growing, size support or fulfillment capacity, or decide whether a bottleneck needs more capacity or better flow.

Capacity and demand planning

This is operational throughput — how much work the organization can absorb. Allocating people across projects is portfolio work, handled in pmo:portfolio-governance.

Forecast demand honestly

Separate the three components, because they need different treatment:

  • Baseline — the steady rate, best estimated from your own history rather than from a plan.
  • Trend — the direction, measured over enough periods to distinguish it from noise.
  • Spikes — launches, seasonality, campaigns, incidents. Known spikes are a planning input; unknown ones are what headroom is for.

Forecast in the unit the work actually arrives in — tickets, orders, shipments, minutes of handling — not in revenue. Revenue divided by an average is a forecast of an average, and averages are where capacity planning goes to die.

Capacity is not headcount

Usable capacity is people multiplied by available hours multiplied by the fraction spent on the work in question. The last term is the one everyone omits and it is rarely above 70%: meetings, training, holiday, and the interruptions that come with the job are real.

Plan against realistic effective capacity. Planning at 100% guarantees the plan fails on its first ordinary week.

Queues tell you before the dashboard does

Utilization above roughly 80% makes wait times rise sharply and non-linearly — a system at 95% is not slightly slower than one at 85%, it is qualitatively worse. This is why "we have spare capacity on paper" coexists with a queue that never clears.

Watch the trend in queue age, not the queue length. A stable-length queue whose oldest item keeps getting older is a queue that is quietly failing its slowest customers.

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

Add capacity or fix flow

Before adding capacity, establish which it is:

  • Genuine capacity shortfall — arrival rate exceeds service rate at reasonable utilization. Add capacity.
  • Flow problem — rework, handoffs, waiting on another team, batching. Adding capacity here adds cost and often makes throughput worse by increasing coordination. Send this to operations:process-design.

The tell: if work spends most of its life waiting rather than being worked, it is a flow problem.

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

  • Plan against nominal headcount rather than effective capacity.
  • Run a critical queue at sustained high utilization and treat the wait times as a mystery.
  • Add capacity to a process you have not measured.
  • Forecast in aggregate currency when work arrives in discrete units.

© 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/operations/skills/capacity-and-demand-planning of cbrock84/headcount.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Capacity And Demand 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.

Capacity And Demand Planning compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Capacity And Demand Planning this skillcbrock84/headcount2k—~814Automated safety check: PassMIT
TimesFM Forecastinggoogle-research/timesfm34k—~4.7kAutomated safety check: PassApache-2.0
StatsmodelszLanqing/codex-claude-academic-skills4.7k15 repos~4.9kAutomated safety check: PassBSD-3-Clause
Timesfm ForecastingzLanqing/codex-claude-academic-skills4.7k3 repos~7.5kAutomated safety check: NotesApache-2.0
Find Hypertable Candidatestimescale/pg-aiguide1.9k1 repos~2.6kAutomated safety check: PassApache-2.0
Pensieve Searcharkohut/pensieve1.4k—~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • TimesFM Forecasting

    google-research/timesfm

    Forecasts any univariate time series zero-shot with Google's TimesFM model, returning point forecasts and calibrated prediction intervals without training.

    34k GitHub stars~4.7k tokensUpdated 11 days ago
    Data & AnalyticsAuto-check passed
  • Statsmodels

    zLanqing/codex-claude-academic-skills

    Statistical models library for Python. An agent skill from zLanqing/codex-claude-academic-skills.

    4.7k GitHub starsUsed in 15 repos~4.9k tokens
    Data & AnalyticsAuto-check passed
  • Timesfm Forecasting

    zLanqing/codex-claude-academic-skills

    Zero-shot time series forecasting with Google's TimesFM foundation model.

    4.7k GitHub starsUsed in 3 repos~7.5k tokens
    Data & AnalyticsAuto-check: notes
  • Find Hypertable Candidates

    timescale/pg-aiguide

    A skill your agent uses to analyze an existing PostgreSQL database and identify which tables should be converted to Timescale/TimescaleDB hypertables.

    1.9k GitHub starsUsed in 1 repo~2.6k tokens
    Data & AnalyticsAuto-check passed
  • Pensieve Search

    arkohut/pensieve

    Search the user's local Pensieve screenshot archive by text, app, or time range.

    1.4k GitHub stars~8.2k tokensUpdated 2 mo ago
    Data & AnalyticsAuto-check passed
  • Alphaear Predictor

    ninehills/skills

    Market prediction skill using Kronos. An agent skill from ninehills/skills.

    280 GitHub starsUsed in 1 repo~531 tokens
    Data & AnalyticsAuto-check passed

More from cbrock84/headcount

All 178 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 23 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 23 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 23 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 23 days ago
    Auto-check passed
  • AI ML Governance

    cbrock84/headcount

    Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.

    2k GitHub stars~1k tokensUpdated 23 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 23 days ago
    Auto-check passed

Questions about Capacity And Demand Planning

What does Capacity And Demand Planning do?

Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity. Capacity And Demand Planning is an agent skill from cbrock84/headcount. Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity.

When should I use Capacity And Demand Planning?

Capacity And Demand Planning fits situations like: tasks that involve Forecasting and time series.

How do I install Capacity And Demand Planning in Claude Code?

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

How do I install Capacity And Demand Planning in Codex?

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

Can I use Capacity And Demand 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 capacity-and-demand-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/capacity-and-demand-planning, .gemini/skills/capacity-and-demand-planning, .github/skills/capacity-and-demand-planning and .opencode/skills/capacity-and-demand-planning in your project.

What does Capacity And Demand Planning need to run?

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

Does Capacity And Demand 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 Capacity And Demand 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 Capacity And Demand Planning use?

Capacity And Demand 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 Capacity And Demand Planning use?

About 814 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 233 tokens, read only when the agent opens those files.

What are the alternatives to Capacity And Demand Planning?

Skills that share tags, products or a category with Capacity And Demand Planning: TimesFM Forecasting (google-research/timesfm, 34k stars), Statsmodels (zLanqing/codex-claude-academic-skills, 4.7k stars), Timesfm Forecasting (zLanqing/codex-claude-academic-skills, 4.7k stars) and Find Hypertable Candidates (timescale/pg-aiguide, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Capacity And Demand Planning?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,022 GitHub stars. The repository holds 178 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.