Capacity Plan
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.
$ npx promptcreek add capacity-planAuto-detects your installed agents and installs the skill to each one.
What This Skill Does
This skill helps analyze team capacity and plan resource allocation for projects. It's designed for project managers, team leads, and resource managers who need to optimize team utilization and forecast resource needs. The skill takes into account team size, workload, upcoming projects, and constraints to generate a capacity plan.
When to Use
- Plan resource allocation for the next quarter.
- Analyze team capacity for a new project.
- Identify potential resource bottlenecks.
- Evaluate the impact of hiring new team members.
- Track team utilization and identify over-allocation.
Key Features
Installation
$ npx promptcreek add capacity-planAuto-detects your installed agents (Claude Code, Cursor, Codex, etc.) and installs the skill to each one.
View Full Skill Content
/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
- [Hire / Contract / Reprioritize / Delay]
- [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.
Supported Agents
Attribution
Details
- License
- MIT
- Source
- admin
- Published
- 3/18/2026
Tags
Related Skills
Decision Logger
Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.
Challenge
/em -challenge — Pre-Mortem Plan Analysis
Postmortem
/em -postmortem — Honest Analysis of What Went Wrong