Skills › Knowledge Work Plugins › capacity-plan
capacity-plan
The facts
Its 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.
The description the agent reads to decide when to use it.
From its settingsline 3
When it starts
The agent would pick this skill when someone is doing resource or headcount planning and wants the numbers — a team that feels overallocated, a quarterly planning cycle coming up, or a decision about whether to hire, contract, or deprioritize work. The description frames it as workload analysis and utilization forecasting, so it fires on capacity questions rather than on individual project scheduling.
Things a person might say (the model's guesses)
- “We're heading into Q3 planning and I need to know if the team can absorb the new roadmap”
- “My engineers are all at 100% and I can't tell if we actually need another hire”
- “Can you stress-test whether these three projects fit the people we have?”
A model's summary of when it is used.
A model's reading
What it takes when started
<team or project scope>
What to type after its name when you start it.
From its settingsline 4
Licence
Apache-2.0, from LICENSE
The terms its author shares it under, which let it be shown here.
From the repositorylicence text
The text
Most marks come from matching words in the file, so treat them as pointers.
1---
2name: capacity-plan
3description: 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.
4argument-hint: "<team or project scope>"
5---
7# /capacity-plan
9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
11Analyze team capacity and plan resource allocation.
/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.
Raw lines 1 to 12Boilerplate, lines 13 to 18. The same text appears in 24 other files here. Close
19## What I Need From You
21- **Team size and roles**: Who do you have?
22- **Current workload**: What are they working on? (Upload from project tracker or describe)
23- **Upcoming work**: What's coming next quarter?
24- **Constraints**: Budget, hiring timeline, skill requirements
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
Raw lines 26 to 2728### People
29- Available headcount and skills
30- Current allocation and utilization
31- Planned hires and timeline
32- Contractor and vendor capacity
People
- Available headcount and skills
- Current allocation and utilization
- Planned hires and timeline
- Contractor and vendor capacity
34### Budget
35- Operating budget by category
36- Project-specific budgets
37- Variance tracking
38- Forecast vs. actual
Budget
- Operating budget by category
- Project-specific budgets
- Variance tracking
- Forecast vs. actual
40### Time
41- Project timelines and dependencies
42- Critical path analysis
43- Buffer and contingency planning
44- Deadline management
Time
- Project timelines and dependencies
- Critical path analysis
- Buffer and contingency planning
- Deadline management
46## Utilization Targets
48| Role Type | Target Utilization | Notes |
49|-----------|-------------------|-------|
50| IC / Specialist | 75-80% | Leave room for reactive work and growth |
51| Manager | 60-70% | Management overhead, meetings, 1:1s |
52| On-call / Support | 50-60% | Interrupt-driven work is unpredictable |
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 |
54## Common Pitfalls
56- Planning to 100% utilization (no buffer for surprises)
57- Ignoring meeting load and context-switching costs
58- Not accounting for vacation, holidays, and sick time
59- Treating all hours as equal (creative work ≠ admin work)
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)
61## Output
63```markdown
64## Capacity Plan: [Team/Project]
65**Period:** [Date range] | **Team Size:** [X]
67### Current Utilization
68| Person/Role | Capacity | Allocated | Available | Utilization |
69|-------------|----------|-----------|-----------|-------------|
70| [Name/Role] | [hrs/wk] | [hrs/wk] | [hrs/wk] | [X]% |
72### Capacity Summary
73- **Total capacity**: [X] hours/week
74- **Currently allocated**: [X] hours/week ([X]%)
75- **Available**: [X] hours/week ([X]%)
76- **Overallocated**: [X people above 100%]
78### Upcoming Demand
79| Project/Initiative | Start | End | Resources Needed | Gap |
80|--------------------|-------|-----|-----------------|-----|
81| [Project] | [Date] | [Date] | [X FTEs] | [Covered/Gap] |
83### Bottlenecks
84- [Skill or role that's oversubscribed]
85- [Time period with a crunch]
87### Recommendations
881. [Hire / Contract / Reprioritize / Delay]
892. [Specific action]
91### Scenarios
92| Scenario | Outcome |
93|----------|---------|
94| Do nothing | [What happens] |
95| Hire [X] | [What changes] |
96| Deprioritize [Y] | [What frees up] |
97```
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] |99## If Connectors Available
101If **~~project tracker** is connected:
102- Pull current workload and ticket assignments automatically
103- Show upcoming sprint or quarter commitments per person
105If **~~calendar** is connected:
106- Factor in PTO, holidays, and recurring meeting load
107- Calculate actual available hours per person
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
Uses an outside tool ~~project :101
Uses an outside tool ~~calendar :105
109## Tips
1111. **Include all work** — BAU, projects, support, meetings. People aren't 100% available for project work.
1122. **Plan for buffer** — Target 80% utilization. 100% means no room for surprises.
1133. **Update regularly** — Capacity plans go stale fast. Review monthly.
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.
From anthropics/knowledge-work-plugins at 2574e29, 2026-10-27. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.