
Capacity Planner
Headcount and delivery-capacity planning, effective capacity from raw headcount...
Install
npx skills add borghei/Claude-Skills --skill capacity-planner -g -a claude-code -y- Repository
- borghei/Claude-Skills1k
- Category
- Testing
- Updated
- 12d ago
- License
- MIT + Commons Clause
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
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.
Capacity Planner
Turns headcount into hours you can actually commit. Most capacity plans fail the same way: they count people instead of delivered hours, ignore ramp, and size supply to fit the roadmap rather than the other way round. This skill computes effective capacity independently, matches it against risk-adjusted demand, and publishes the cut line.
When to use this skill
- Quarterly planning, deciding what the team can commit to for the next 90 days
- Testing a roadmap, a stakeholder has a list and wants to know if it fits
- Building a hiring ask, quantifying a structural gap in hours and dollars
- Hire vs contract vs defer, choosing how to close a capacity shortfall
- Mid-quarter replan, the burn rate diverged and commitments need renegotiating
- Onboarding impact, modelling what three new hires actually deliver this quarter
Inputs the skill expects
- Team roster: name, discipline, seniority, FTE, tenure in months
- Known absence: booked PTO days, on-call rotation weeks per person
- Overhead estimates: meeting load and non-delivery overhead as a percentage
- Working days and hours per day for the period
- Candidate commitments with discipline, hour estimate, confidence band, and priority
- For scenario work: demand curve per quarter, salary/contractor rates, start dates
Clarify First
Before generating, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.


