capacity-plan

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/capacity-plan

/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.
如果您看到不熟悉的占位符或需要查看已连接的工具,请参阅CONNECTORS.md
分析团队容量并规划资源分配。

Usage

使用方法

/capacity-plan $ARGUMENTS
/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 TypeTarget UtilizationNotes
IC / Specialist75-80%Leave room for reactive work and growth
Manager60-70%Management overhead, meetings, 1:1s
On-call / Support50-60%Interrupt-driven work is unpredictable
角色类型目标利用率说明
IC / 专家75-80%预留应对突发工作和个人成长的时间
经理60-70%包含管理事务、会议、一对一沟通的时间开销
值班/支持人员50-60%响应式工作具有不可预测性

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)
  • 按100%利用率规划(未预留应对突发情况的缓冲时间)
  • 忽略会议负载和上下文切换成本
  • 未考虑休假、节假日和病假时间
  • 认为所有工时价值相同(创意工作 ≠ 行政工作)

Output

输出格式

markdown
undefined
markdown
undefined

Capacity Plan: [Team/Project]

容量规划:[团队/项目]

Period: [Date range] | Team Size: [X]
周期: [日期范围] | 团队规模: [X]

Current Utilization

当前利用率

Person/RoleCapacityAllocatedAvailableUtilization
[Name/Role][hrs/wk][hrs/wk][hrs/wk][X]%
人员/角色可用容量已分配工时剩余可用利用率
[姓名/角色][小时/周][小时/周][小时/周][X]%

Capacity Summary

容量汇总

  • Total capacity: [X] hours/week
  • Currently allocated: [X] hours/week ([X]%)
  • Available: [X] hours/week ([X]%)
  • Overallocated: [X people above 100%]
  • 总可用容量:[X] 小时/周
  • 已分配工时:[X] 小时/周 ([X]%)
  • 剩余可用:[X] 小时/周 ([X]%)
  • 过载人员:[X人利用率超过100%]

Upcoming Demand

后续需求

Project/InitiativeStartEndResources NeededGap
[Project][Date][Date][X FTEs][Covered/Gap]
项目/计划开始时间结束时间所需资源缺口情况
[项目][日期][日期][X名全职人员][已覆盖/存在缺口]

Bottlenecks

瓶颈

  • [Skill or role that's oversubscribed]
  • [Time period with a crunch]
  • [需求过剩的技能或角色]
  • [存在时间压力的阶段]

Recommendations

建议

  1. [Hire / Contract / Reprioritize / Delay]
  2. [Specific action]
  1. [招聘 / 外包 / 调整优先级 / 延迟项目]
  2. [具体行动]

Scenarios

场景分析

ScenarioOutcome
Do nothing[What happens]
Hire [X][What changes]
Deprioritize [Y][What frees up]
undefined
场景结果
不采取任何行动[会发生什么]
招聘[X人][会有哪些变化]
降低[Y项目]优先级[会释放哪些资源]
undefined

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

提示

  1. Include all work — BAU, projects, support, meetings. People aren't 100% available for project work.
  2. Plan for buffer — Target 80% utilization. 100% means no room for surprises.
  3. Update regularly — Capacity plans go stale fast. Review monthly.
  1. 涵盖所有工作内容——日常运营、项目、支持工作、会议。人员不可能100%投入到项目工作中。
  2. 预留缓冲时间——目标利用率设为80%。100%意味着没有应对突发情况的空间。
  3. 定期更新——容量规划会很快过时。建议每月回顾更新。