Claude Skill MartBrowse skillsWhat is a Skill?
 
← Back to list

Ops Capacity Planner

Sizes ops headcount, flags utilization risk, and sequences a 12-month hiring plan using Erlang-C queueing math.

Data & AnalyticsIntermediate★ 24,151⑂ 3,405AI score 8/10Last updated: Aug 9, 2026

What it does

Sizes teams that handle queued work — Support, CX, Customer Success, BizOps, IT ops, Finance ops — with arithmetic instead of vibes. Backed by Erlang-C queueing theory, Little's Law, and deterministic stdlib-only Python scripts (no LLM calls), it produces three artifacts:

  1. Capacity sizing — required FTE at 70/80/90% utilization against P50/P90/P99 demand, with P(SLA breach) at each point and a SAFE/WATCH/AT_RISK/CRITICAL band.
  2. Utilization health — per-member traffic lights plus a team verdict (HEALTHY/SQUEEZED/OVERLOADED/UNBALANCED) with variance detection.
  3. 12-month quarterly hiring plan — ramp curves, attrition, QoQ demand growth, max-hires-per-quarter limits, and a manager-hire trigger at 7 ICs/manager.

It also ships an 11-item anti-pattern taxonomy, a curated queueing/workforce reference canon, and a seven-question "forcing" interview you must answer in order before committing a headcount budget.

Who it's for

  • Ops leaders sitting above 80% sustained utilization or growing the team >50% in 12 months.
  • Heads of Support/CX who need to defend a headcount ask to the CFO with numbers.
  • BizOps teams diagnosing whether SLA misses are a sizing, process, or bottleneck problem.
  • M&A or new-segment launches that require sizing a brand-new or merged org.

Not for engineering throughput (use a DORA-based skill) or 1–5 year strategic workforce planning.

Examples

  1. Annual planning: feed P50 320 / P90 480 / P99 720 tickets per day, 12-min AHT, 30-min SLA, 18 current FTE, 30% shrinkage — read the 80% utilization row for your sizing point and the breach probabilities for your surge exposure.
  2. Burnout early warning: run the utilization analyzer on real per-agent data to find anyone sustained above 85% and check whether the team spread exceeds 30 points (UNBALANCED) before you hire anyone.
  3. Hiring sequence: 20 FTE today, 32 by year end, 6-week ramp, 30% annual attrition — get quarterly hire counts front-loaded to Q1 plus the quarter your first new manager is needed.

· · · Install guide · · ·

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the .gemini/skills/capacity-planner folder from the GitHub repo alirezarezvani/claude-skills into my ~/.claude/skills/capacity-planner/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/alirezarezvani/claude-skills.git && mkdir -p ~/.claude/skills && cp -r claude-skills/.gemini/skills/capacity-planner ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal.
  2. Clone the repo: git clone https://github.com/alirezarezvani/claude-skills.git
  3. Create the skills directory: mkdir -p ~/.claude/skills
  4. Copy the skill: cp -r claude-skills/.gemini/skills/capacity-planner ~/.claude/skills/
  5. Confirm Python 3 is available: python3 --version
  6. Smoke test: cd ~/.claude/skills/capacity-planner && python3 scripts/capacity_modeler.py --sample
  7. Restart Claude Code and ask something like "size my support team capacity" or "build next year's headcount plan".
  8. For real data, fill in the JSON skeletons in assets/capacity_brief_template.md and pass them with --input <path>.
View source on GitHub ↗License: MIT