Generated banner for Capacity Plan
Generated logo for Capacity Plan

Capacity Plan

AnthropicOfficialPublished by Anthropic

  • Skill
  • Content generator
  • Business and productivity
  • Apache-2.0
  • No issues found

From the author

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.
— the description by Anthropic

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The capacity-plan skill assists in evaluating team workload and resource availability. It processes information regarding team composition, current project commitments, and upcoming initiatives to generate a structured capacity report. By accounting for utilization targets, potential bottlenecks, and various planning scenarios, it helps teams make informed decisions about hiring, project prioritization, and timeline management.

What it does

  • Analyzes current team workload and resource allocation
  • Forecasts capacity against upcoming project demand
  • Identifies potential bottlenecks and oversubscribed roles
  • Provides actionable recommendations for hiring or reprioritization
  • Generates comparative scenarios to evaluate different planning outcomes
  • Integrates with project trackers and calendars to pull data on commitments and availability

When to use it

  • During quarterly planning sessions
  • When the team feels overallocated and requires data-driven insights
  • When deciding whether to hire new staff or deprioritize existing projects
  • When stress-testing project feasibility against current team capacity

Advantages

  • Promotes realistic planning by accounting for non-project work and buffers
  • Provides clear visibility into team utilization and resource gaps
  • Supports data-backed decision making for resource management
  • Helps prevent burnout by identifying overallocated team members

Usage examples

“capacity-plan for the engineering team for Q3”
Generates a report detailing current utilization, upcoming project demand, identified bottlenecks, and recommendations for the engineering team's Q3 capacity.
“capacity-plan for the marketing department using my project tracker data”
Produces a capacity analysis based on the team's current project commitments and available hours, highlighting potential resource gaps.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/anthropics/capacity-plan/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip capacity-plan.zip -d .agents/skills

Documentation by Anthropic

/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 TypeTarget UtilizationNotes
IC / Specialist75-80%Leave room for reactive work and growth
Manager60-70%Management overhead, meetings, 1:1s
On-call / Support50-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

  1. Include all work — BAU, projects, support, meetings. People aren't 100% available for project work.

  2. Plan for buffer — Target 80% utilization. 100% means no room for surprises.

  3. Update regularly — Capacity plans go stale fast. Review monthly.

Files

SKILL.md

/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 TypeTarget UtilizationNotes
IC / Specialist75-80%Leave room for reactive work and growth
Manager60-70%Management overhead, meetings, 1:1s
On-call / Support50-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

  1. Include all work — BAU, projects, support, meetings. People aren't 100% available for project work.

  2. Plan for buffer — Target 80% utilization. 100% means no room for surprises.

  3. Update regularly — Capacity plans go stale fast. Review monthly.

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Claude Code frontmatter

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Anthropic
Publisher
Anthropic (Official)
Source
anthropics/knowledge-work-plugins · operations/skills/capacity-plan · commit e050c2e
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Anthropic or Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download capacity-plan.zip