Capacity Plan

1---2name: capacity-plan3description: 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---6 7# /capacity-plan8 9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).10 11Analyze team capacity and plan resource allocation.12 13## Usage14 15```16/capacity-plan $ARGUMENTS17```18 19## What I Need From You20 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 requirements25 26## Planning Dimensions27 28### People29- Available headcount and skills30- Current allocation and utilization31- Planned hires and timeline32- Contractor and vendor capacity33 34### Budget35- Operating budget by category36- Project-specific budgets37- Variance tracking38- Forecast vs. actual39 40### Time41- Project timelines and dependencies42- Critical path analysis43- Buffer and contingency planning44- Deadline management45 46## Utilization Targets47 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 |53 54## Common Pitfalls55 56- Planning to 100% utilization (no buffer for surprises)57- Ignoring meeting load and context-switching costs58- Not accounting for vacation, holidays, and sick time59- Treating all hours as equal (creative work ≠ admin work)60 61## Output62 63```markdown64## Capacity Plan: [Team/Project]65**Period:** [Date range] | **Team Size:** [X]66 67### Current Utilization68| Person/Role | Capacity | Allocated | Available | Utilization |69|-------------|----------|-----------|-----------|-------------|70| [Name/Role] | [hrs/wk] | [hrs/wk] | [hrs/wk] | [X]% |71 72### Capacity Summary73- **Total capacity**: [X] hours/week74- **Currently allocated**: [X] hours/week ([X]%)75- **Available**: [X] hours/week ([X]%)76- **Overallocated**: [X people above 100%]77 78### Upcoming Demand79| Project/Initiative | Start | End | Resources Needed | Gap |80|--------------------|-------|-----|-----------------|-----|81| [Project] | [Date] | [Date] | [X FTEs] | [Covered/Gap] |82 83### Bottlenecks84- [Skill or role that's oversubscribed]85- [Time period with a crunch]86 87### Recommendations881. [Hire / Contract / Reprioritize / Delay]892. [Specific action]90 91### Scenarios92| Scenario | Outcome |93|----------|---------|94| Do nothing | [What happens] |95| Hire [X] | [What changes] |96| Deprioritize [Y] | [What frees up] |97```98 99## If Connectors Available100 101If **~~project tracker** is connected:102- Pull current workload and ticket assignments automatically103- Show upcoming sprint or quarter commitments per person104 105If **~~calendar** is connected:106- Factor in PTO, holidays, and recurring meeting load107- Calculate actual available hours per person108 109## Tips110 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.