capacity-planner
FeaturedUse 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).
Install
Quality Score: 97/100
Skill Content
Details
- Author
- alirezarezvani
- Repository
- alirezarezvani/claude-skills
- Created
- 11 months ago
- Last Updated
- 3 weeks ago
- Language
- Python
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
ops-capacity-planner
Size an ops team (support, CX, IT, finance ops) that handles queued work — utilization bands, demand P90, shrinkage-adjusted FTE, hiring sequence. Use when user says "capacity planning", "headcount plan", "utilization", "SLA understaffed". Not engineering velocity.
ops-capacity-planner
Size an ops team (support, CX, IT, finance ops) that handles queued work — utilization bands, demand P90, shrinkage-adjusted FTE, hiring sequence. Use when user says "capacity planning", "headcount plan", "인력 계획", "utilization", "가동률", "채용 계획", "SLA understaffed". Not engineering velocity.
capacity-planner
Headcount and delivery-capacity planning — effective capacity from raw headcount, hire/contract/defer scenarios, and capacity-vs-commitment gap reports. Use when planning a quarter, sizing a hiring ask, or testing whether a roadmap fits.