capacity-planner

Use when an ops leader (Director of CX, Head of Support, VP Ops, Head of BizOps, Head of IT ops, Head of Finance ops) is sizing ops capacity, building a headcount plan, modeling utilization risk, planning Q3 capacity or annual support capacity, or designing CS coverage — and needs Erlang-C queueing math, P90 demand sizing, shrinkage-adjusted FTE, manager-trigger thresholds, and a quarterly hiring sequence with ramp + attrition. Apply when sustained team utilization is above 80% or when the team is growing >50% in 12 months. Run before committing the headcount budget. This is NOT engineering capacity (see vpe-advisor for DORA + cycle time) and NOT strategic 3-year workforce planning (see chro-advisor).

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable ops-capacity skill: clean workflow with validation gates and a checklist, good progressive disclosure to real reference/script/asset bundles, and no padding of known concepts. Minor conciseness and inline-example gaps keep it just short of perfect.

Suggestions

Trim the full bibliographic citations in the Forcing-question library to author + short title (e.g., 'Goldratt, The Goal') to reduce tokens without losing grounding.

Show a minimal inline JSON input skeleton for one script so the input shape is visible without opening the asset template.

Consider moving the seven forcing questions to a references file and keeping only the discipline preamble plus a one-line-per-question summary in SKILL.md.

Dimension	Reasoning	Score
Conciseness	Dense and largely free of concepts Claude already knows (no 'what is Erlang-C' padding), but the full bibliographic citations in the Forcing-question library ('Eli Goldratt, The Goal, 1984'; 'Hopp & Spearman, Factory Physics, 3rd ed., 2008') and some 'Why it matters' prose add tokens that could be trimmed without losing clarity.	4 / 5
Actionability	Concrete, executable guidance throughout — named scripts with specific flags (--profile, --input, --output, --sample, --help) and a copy-paste quick example — but the actual JSON input/output shape is deferred to the asset template rather than shown inline, leaving a minor gap.	4 / 5
Workflow Clarity	Five-step workflow is clearly sequenced with explicit validation gates (Step 1: 'If you only have averages, stop and pull the distribution'; Step 3: '>85% sustained is a throughput-collapse risk', 'fix that before hiring') and a forcing-question checklist with feedback loops ('If you can't answer one, that is your next investigation').	5 / 5
Progressive Disclosure	SKILL.md is a clear overview with well-signaled one-level-deep references to real bundle files — references/queueing_theory_canon.md, ops_workforce_planning_canon.md, capacity_anti_patterns.md, scripts/*.py, assets/capacity_brief_template.md — each described with its contents and source count; no nested reference chains.	5 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exceptionally strong description: it states concrete capabilities, natural trigger terms for multiple ops-leader roles, explicit when-conditions, and clear disambiguation against adjacent skills. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'sizing ops capacity', 'building a headcount plan', 'modeling utilization risk', 'designing CS coverage' — plus concrete deliverables ('Erlang-C queueing math, P90 demand sizing, shrinkage-adjusted FTE, manager-trigger thresholds, quarterly hiring sequence with ramp + attrition'), giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what (sizing/headcount/utilization/hiring-plan with named math) and when ('Use when an ops leader...', 'Apply when sustained team utilization is above 80%...', 'Run before committing the headcount budget') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases an ops leader would actually say are covered comprehensively with synonyms — role titles (Director of CX, Head of Support, VP Ops, etc.) and trigger phrases ('sizing ops capacity', 'headcount plan', 'utilization risk', 'annual support capacity', 'CS coverage', 'utilization above 80%', 'growing >50% in 12 months').	5 / 5
Distinctiveness Conflict Risk	Clear niche (ops queued-work capacity) with explicit boundaries — 'This is NOT engineering capacity (see vpe-advisor...) and NOT strategic 3-year workforce planning (see chro-advisor)' — minimizing conflict risk with sibling skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: business-operations/skills/capacity-planner/SKILL.md
Commit: 19392f7

Reviewed: ~1 hour ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.