---
id: daily-capacity-plan
name: "capacity-plan"
url: https://skills.yangsir.net/skill/daily-capacity-plan
author: anthropics
domain: ai-project-management-collaboration
tags: ["planning", "resource-management", "team", "analytics", "ai-engineering"]
install_count: 2800
rating: 4.40 (20 reviews)
github: https://github.com/anthropics/knowledge-work-plugins
---

# capacity-plan

> 分析团队产能并规划资源分配，计算人员利用率、预算分配和时间管理，支持项目资源优化决策。

**Stats**: 2,800 installs · 4.4/5 (20 reviews)

## Before / After 对比

### 优化团队产能与资源分配

**Before**:

在引入 capacity-plan 技能之前，团队的产能规划和资源分配是一个耗时且易出错的手动过程。项目经理或团队负责人需手动收集各成员的工时表、项目进度报告，并从不同工具中汇总数据。他们人工计算利用率，并尝试识别潜在瓶颈。这个过程涉及大量数据整理、复杂计算和反复沟通。由于缺乏统一视图和自动化分析，很容易出现规划不足（如未考虑会议、假期）或过度规划（如将利用率定为 100%）的情况，导致资源分配不均、项目延期或团队成员倦怠。决策往往基于经验而非实时数据，效率低下且风险较高。

**After**:

通过使用 capacity-plan 技能，团队的产能规划和资源分配变得高效且数据驱动。只需提供团队规模、角色、当前和即将到来的工作量以及约束条件，技能就能自动分析并生成一份结构化的产能计划。它能精确计算每个成员的利用率，汇总团队总容量，并清晰指出超负荷人员和潜在的技能或时间瓶颈。技能还会根据分析结果提出具体的优化建议，例如“招聘”、“外包”或“重新排优先级”，甚至能模拟不同场景的潜在结果。这极大地减少了手动计算和数据整合时间，提高了规划准确性，帮助团队避免常见规划陷阱，确保资源得到最优化配置，支持项目顺利进行。

| Metric | Before | After | Change |
|---|---|---|---|
| 规划周期时长 | 2天 | 0.5天 | -75% |
| 资源利用率计算准确性 | 70% | 95% | +35.71% |
| 识别瓶颈所需时间 | 8小时 | 0.1小时 | -98.75% |
| 超负荷资源比例 | 30% | 5% | -83.33% |

## Readme

# capacity-plan

# /capacity-plan

If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/operations/skills/capacity-plan/../../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
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.

Weekly Installs328Repository[anthropics/know…-plugins](https://github.com/anthropics/knowledge-work-plugins)GitHub Stars10.6KFirst SeenMar 13, 2026Security Audits[Gen Agent Trust HubPass](/anthropics/knowledge-work-plugins/capacity-plan/security/agent-trust-hub)[SocketPass](/anthropics/knowledge-work-plugins/capacity-plan/security/socket)[SnykPass](/anthropics/knowledge-work-plugins/capacity-plan/security/snyk)Installed oncodex315gemini-cli313opencode312cursor312kimi-cli311github-copilot311

---
*Source: https://skills.yangsir.net/skill/daily-capacity-plan*
*Markdown mirror: https://skills.yangsir.net/api/skill/daily-capacity-plan/markdown*