AI SkillPlan capacityOperations
Show whether upcoming work fits the people, time, budget, and skills you actually have. — Claude Skill
A Claude Skill for Claude Code by Anthropic✓ — run /capacity-plan in Claude·Updated Jun 13, 2026·vmain@da04ccb
Analyzes team capacity, utilization, upcoming demand, bottlenecks, and scenarios so teams can hire, contract, delay, or deprioritize with evidence.
- Calculates utilization by role and compares it to realistic targets.
- Separates current allocation from available capacity.
- Shows upcoming demand and the specific skill or time gap.
- Compares scenarios such as do nothing, hire, contract, delay, or deprioritize.
YouToday
Teams commit to work based on headcount, without accounting for meetings, support load, PTO, or skill bottlenecks.
With /capacity-plan
Run /capacity-plan to compare real capacity with committed demand and choose hire, contract, delay, or deprioritize.
1 List team and capacity2 Add current and upcoming work3 Calculate utilization4 Compare scenarios
Who this is for
What it does
Quarterly planning
Stress-test whether the roadmap fits available people and time.
Overallocated team review
Show which roles are above target utilization and what to move.
Hire or deprioritize decision
Compare scenarios before asking for budget or cutting scope.
How it works
1
Collect team size, roles, current workload, upcoming projects, constraints, and timelines.
2
Estimate practical weekly capacity after meetings, support load, and PTO.
3
Compare allocation to utilization targets by role type.
4
List demand gaps and bottlenecks by initiative.
5
Recommend hiring, contractor support, sequencing, or scope reduction.
Input options
Team size and roles
People, roles, capacity, skill sets, and planned hires.
Example
Team and demand
Team: 2 support specialists, 1 support lead, 1 knowledge manager Available hours after meetings/PTO: specialists 30h/wk each, lead 24h/wk, knowledge manager 28h/wk Current work: ticket queue 52h/wk, escalations 18h/wk, help center refresh 20h/wk, launch readiness 24h/wk Upcoming Q3 work: onboarding launch support, SSO article refresh, migration weekend coverage Need: utilization, bottlenecks, recommendations, scenarios.
Capacity plan
Capacity Plan: Support Operations Q3
**Period:** Q3 planning **Team Size:** 4 **Planning target:** keep specialists under 80%, support lead under 70%, and interrupt-driven work under 60% where possible.
Current utilization
| Person/Role | Capacity | Allocated | Available | Utilization | |---|---:|---:|---:|---:| | Support Specialist A | 30h/wk | 32h/wk | -2h/wk | 107% | | Support Specialist B | 30h/wk | 29h/wk | 1h/wk | 97% | | Support Lead | 24h/wk | 23h/wk | 1h/wk | 96% | | Knowledge Manager | 28h/wk | 30h/wk | -2h/wk | 107% |
Capacity summary
- Total practical capacity: 112 hours/week - Currently allocated: 114 hours/week (102%) - Available: -2 hours/week - Overallocated: 3 people above realistic target - Main bottleneck: knowledge manager time for launch docs and SSO refresh
Upcoming demand
| Project/Initiative | Start | End | Resources Needed | Gap | |---|---|---|---|---| | Onboarding launch support | Jun 17 | Jul 15 | 20h/wk support + 12h/wk docs | Gap: 14h/wk | | SSO article refresh | Jul 1 | Jul 20 | 10h/wk knowledge manager | Gap: 10h/wk | | Migration weekend coverage | Aug 10 | Aug 12 | 2 specialists on call | Covered only if ticket queue is reduced |
Recommendations and scenarios
| Scenario | Outcome | |---|---| | Do nothing | Queue response time worsens and launch docs slip | | Add contractor writer for 6 weeks | Frees 10h/wk from knowledge manager and protects launch docs | | Delay SSO refresh by 3 weeks | Launch becomes feasible, but enterprise support risk remains | | Reduce launch scope | Lowers specialist load by 8h/wk but may increase post-launch confusion | Recommended action: add temporary writing support and delay SSO refresh unless enterprise launch depends on it.
Metrics this improves
Board Prep Time
Creates evidence for hiring, contractor, and deprioritization decisions.
OperationsStrategic vs Reactive Work
Shows how much capacity is spent on planned work versus reactive demand.
OperationsSprint Predictability
Reduces overcommitment by matching work to realistic capacity.
OperationsWorks with
Want to use Capacity Plan?
Choose how to get started.
Run in Claude Code
Free. Open source.
Install and run this skill locally on your computer.
1
Install Claude Code
Open a terminal on your computer and paste this command:
2
Install the skill
This downloads the skill with all its files to your computer:
Add -g at the end to make it available in all your projects.
3
View source on GitHub Run it
Start Claude Code, then type the command:
then
/capacity-plan
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Analyze team capacity and plan resource allocation.
Usage
/capacity-plan $ARGUMENTS
What I Need From You
- Team size and roles: Who do you have?
- Current workload: What are they working on? (Upload from project tracker or describe)
- Upcoming work: What's coming next quarter?
- Constraints: Budget, hiring timeline, skill requirements
Planning Dimensions
People
- Available headcount and skills
- Current allocation and utilization
- Planned hires and timeline
- Contractor and vendor capacity
Budget
- Operating budget by category
- Project-specific budgets
- Variance tracking
- Forecast vs. actual
Time
- Project timelines and dependencies
- Critical path analysis
- Buffer and contingency planning
- Deadline management
Utilization Targets
| Role Type | Target Utilization | Notes |
|---|---|---|
| IC / Specialist | 75-80% | Leave room for reactive work and growth |
| Manager | 60-70% | Management overhead, meetings, 1:1s |
| On-call / Support | 50-60% | Interrupt-driven work is unpredictable |
Common Pitfalls
- Planning to 100% utilization (no buffer for surprises)
- Ignoring meeting load and context-switching costs
- Not accounting for vacation, holidays, and sick time
- Treating all hours as equal (creative work ≠ admin work)
Output
## Capacity Plan: [Team/Project]
**Period:** [Date range] | **Team Size:** [X]
### Current Utilization
| Person/Role | Capacity | Allocated | Available | Utilization |
|-------------|----------|-----------|-----------|-------------|
| [Name/Role] | [hrs/wk] | [hrs/wk] | [hrs/wk] | [X]% |
### Capacity Summary
- **Total capacity**: [X] hours/week
- **Currently allocated**: [X] hours/week ([X]%)
- **Available**: [X] hours/week ([X]%)
- **Overallocated**: [X people above 100%]
### Upcoming Demand
| Project/Initiative | Start | End | Resources Needed | Gap |
|--------------------|-------|-----|-----------------|-----|
| [Project] | [Date] | [Date] | [X FTEs] | [Covered/Gap] |
### Bottlenecks
- [Skill or role that's oversubscribed]
- [Time period with a crunch]
### Recommendations
1. [Hire / Contract / Reprioritize / Delay]
2. [Specific action]
### Scenarios
| Scenario | Outcome |
|----------|---------|
| Do nothing | [What happens] |
| Hire [X] | [What changes] |
| Deprioritize [Y] | [What frees up] |
If Connectors Available
If ~~project tracker is connected:
- Pull current workload and ticket assignments automatically
- Show upcoming sprint or quarter commitments per person
If ~~calendar is connected:
- Factor in PTO, holidays, and recurring meeting load
- Calculate actual available hours per person
Tips
- Include all work — BAU, projects, support, meetings. People aren't 100% available for project work.
- Plan for buffer — Target 80% utilization. 100% means no room for surprises.
- Update regularly — Capacity plans go stale fast. Review monthly.
Reference documents
name: capacity-plan description: 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. argument-hint: "<team or project scope>"
/capacity-plan
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Analyze team capacity and plan resource allocation.
Usage
/capacity-plan $ARGUMENTS
What I Need From You
- Team size and roles: Who do you have?
- Current workload: What are they working on? (Upload from project tracker or describe)
- Upcoming work: What's coming next quarter?
- Constraints: Budget, hiring timeline, skill requirements
Planning Dimensions
People
- Available headcount and skills
- Current allocation and utilization
- Planned hires and timeline
- Contractor and vendor capacity
Budget
- Operating budget by category
- Project-specific budgets
- Variance tracking
- Forecast vs. actual
Time
- Project timelines and dependencies
- Critical path analysis
- Buffer and contingency planning
- Deadline management
Utilization Targets
| Role Type | Target Utilization | Notes |
|---|---|---|
| IC / Specialist | 75-80% | Leave room for reactive work and growth |
| Manager | 60-70% | Management overhead, meetings, 1:1s |
| On-call / Support | 50-60% | Interrupt-driven work is unpredictable |
Common Pitfalls
- Planning to 100% utilization (no buffer for surprises)
- Ignoring meeting load and context-switching costs
- Not accounting for vacation, holidays, and sick time
- Treating all hours as equal (creative work ≠ admin work)
Output
## Capacity Plan: [Team/Project]
**Period:** [Date range] | **Team Size:** [X]
### Current Utilization
| Person/Role | Capacity | Allocated | Available | Utilization |
|-------------|----------|-----------|-----------|-------------|
| [Name/Role] | [hrs/wk] | [hrs/wk] | [hrs/wk] | [X]% |
### Capacity Summary
- **Total capacity**: [X] hours/week
- **Currently allocated**: [X] hours/week ([X]%)
- **Available**: [X] hours/week ([X]%)
- **Overallocated**: [X people above 100%]
### Upcoming Demand
| Project/Initiative | Start | End | Resources Needed | Gap |
|--------------------|-------|-----|-----------------|-----|
| [Project] | [Date] | [Date] | [X FTEs] | [Covered/Gap] |
### Bottlenecks
- [Skill or role that's oversubscribed]
- [Time period with a crunch]
### Recommendations
1. [Hire / Contract / Reprioritize / Delay]
2. [Specific action]
### Scenarios
| Scenario | Outcome |
|----------|---------|
| Do nothing | [What happens] |
| Hire [X] | [What changes] |
| Deprioritize [Y] | [What frees up] |
If Connectors Available
If ~~project tracker is connected:
- Pull current workload and ticket assignments automatically
- Show upcoming sprint or quarter commitments per person
If ~~calendar is connected:
- Factor in PTO, holidays, and recurring meeting load
- Calculate actual available hours per person
Tips
- Include all work — BAU, projects, support, meetings. People aren't 100% available for project work.
- Plan for buffer — Target 80% utilization. 100% means no room for surprises.
- Update regularly — Capacity plans go stale fast. Review monthly.