Operations

Skill 80 of 200

Capacity Plan

Plan resource capacity — workload analysis and utilization forecasting.

1 minute · 259 words · 11 sections

Install

$ npx skills add anthropics/knowledge-work-plugins --skill capacity-plan

$ npx skills add anthropics/knowledge-work-plugins

» /plugin marketplace add anthropics/knowledge-work-plugins

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md (opens in a new tab).

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.

About this skill

Trigger

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 verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/anthropics/knowledge-work-plugins, branch main, last pushed 23 September 2026.

Licence

Apache-2.0 — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

200 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 27 distinct layouts observed: bio-research/skills/*/SKILL.md, cowork-plugin-management/skills/*/SKILL.md, customer-support/skills/*/SKILL.md, data/skills/*/SKILL.md, design/skills/*/SKILL.md, engineering/skills/*/SKILL.md, enterprise-search/skills/*/SKILL.md, finance/skills/*/SKILL.md, human-resources/skills/*/SKILL.md, legal/skills/*/SKILL.md, marketing/skills/*/SKILL.md, operations/skills/*/SKILL.md, partner-built/apollo/skills/*/SKILL.md, partner-built/brand-voice/skills/*/SKILL.md, partner-built/common-room/skills/*/SKILL.md, partner-built/slack/skills/*/SKILL.md, partner-built/zoom-plugin/skills/*/SKILL.md, partner-built/zoom-plugin/skills/contact-center/*/SKILL.md, partner-built/zoom-plugin/skills/meeting-sdk/*/SKILL.md, partner-built/zoom-plugin/skills/meeting-sdk/web/*/SKILL.md, partner-built/zoom-plugin/skills/video-sdk/*/SKILL.md, partner-built/zoom-plugin/skills/virtual-agent/*/SKILL.md, partner-built/zoom-plugin/skills/zoom-mcp/*/SKILL.md, pdf-viewer/skills/*/SKILL.md, product-management/skills/*/SKILL.md, productivity/skills/*/SKILL.md, sales/skills/*/SKILL.md.

Issue colours

Resolved from the awesome-design-md registry — hue 39°, chroma 0.113. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Typefaces

Display: Copernicus is not available to us; set in Newsreader.

We never load a typeface at request time from a third-party origin, so a brand face we do not already self-host is substituted rather than fetched.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Removed “/capacity-plan”, a leading h1 that duplicated the skill title.

Spec compliance

53 editorial notes across 41 of 200 skills. They are printed in the margin of each skill rather than as errors here.

and 31 more.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Anthropic, declaring 120 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /anthropics/knowledge-work-plugins.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md (opens in a new tab).

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.