capacity-plan
Plan resource capacity — workload analysis and utilization forecasting. Use when heading into quarterly planning, the team feels overallocated and you need the numbers, deciding whether to hire or deprioritize, or stress-testing whether upcoming projects fit the people you have.
Security Assessment
About capacity-plan
A planning aid for analyzing team capacity and allocating resources across people, budget, and time. It is aimed at moments when the numbers matter: quarterly planning, a team that feels overallocated, hire-versus-deprioritize decisions, or stress-testing whether upcoming projects actually fit the people available. To run, it asks for team size and roles, current workload (pulled from a project tracker or described), upcoming work for the next quarter, and constraints such as budget, hiring timeline, and skill requirements.
Analysis spans three dimensions. People covers available headcount and skills, current allocation and utilization, planned hires, and contractor capacity. Budget covers operating and project budgets, variance, and forecast versus actual. Time covers project timelines and dependencies, critical-path analysis, and buffer or contingency planning. It applies role-based utilization targets rather than assuming everyone is fully available, roughly 75-80% for ICs and specialists, 60-70% for managers, and 50-60% for on-call or support roles, leaving room for reactive work, meetings, and growth. It also calls out common pitfalls: planning to 100% utilization, ignoring meeting load and context-switching, and forgetting vacation, holidays, and sick time.
The output is a structured markdown capacity plan: a current-utilization table per person or role, a capacity summary (total, allocated, available, overallocated), an upcoming-demand table with resource gaps, identified bottlenecks, prioritized recommendations (hire, contract, reprioritize, or delay), and side-by-side scenarios comparing outcomes. When connectors are available it can go further: a connected project tracker pulls current workload and sprint or quarter commitments per person, and a connected calendar factors in PTO, holidays, and recurring meeting load to compute actual available hours. The guiding advice is to include all work (BAU, projects, support, meetings), plan for buffer by targeting around 80% utilization, and revisit the plan monthly because capacity plans go stale quickly.
FAQ
What information do I need to provide?
Team size and roles, current workload, upcoming work for the next quarter, and constraints like budget, hiring timeline, and skill requirements.
What utilization targets does it use?
About 75-80% for ICs and specialists, 60-70% for managers, and 50-60% for on-call or support roles, deliberately leaving buffer instead of planning to 100%.
Does it require integrations to work?
No, but connectors help. A connected project tracker auto-pulls workload and commitments, and a connected calendar factors in PTO, holidays, and meeting load for actual available hours.
What does the output look like?
A markdown plan with current-utilization and upcoming-demand tables, a capacity summary, bottlenecks, prioritized recommendations, and comparative scenarios (do nothing, hire, or deprioritize).
When should I use it?
Heading into quarterly planning, when the team feels overallocated and you need the numbers, when deciding whether to hire or deprioritize, or when stress-testing whether projects fit your people.
Install capacity-plan
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
anthropics/knowledge-work-plugins