什么是 容量规划器？

容量规划器是一款复杂的资源管理工具，旨在改变组织处理工作负载分配和基础设施扩展的方式。作为 Openclaw Skills 系列的一部分，它通过分析团队规模、利用率和项目管线来生成预测模型，在潜在瓶颈影响运营前 4 到 8 周发出预警。

该技能通过提供定量规划框架，使领导者能够超越直觉进行决策。它确保每项新项目或招聘决策都有数据支持，在 Openclaw Skills 环境中保持生产力与可持续增长之间的健康平衡。

下载入口:https://github.com/openclaw/skills/tree/main/skills/1kalin/afrexai-capacity-planner

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

容量规划器 应用场景

• 在手动估算感觉像凭空猜测时管理冲刺计划
• 评估入驻新客户或高风险项目的可行性
• 用硬数据而非直觉验证招聘需求
• 预测并应对季节性流量高峰期间的基础设施压力

1. 该技能通过将团队成员映射到活跃承诺并计算真实利用率来审计您当前的负载。
2. 它模拟多种“假设”场景，如团队流失、范围蔓延或新项目加入。
3. 系统标记运营风险，识别单点故障和截止日期集群。
4. 它根据特定指标生成可操作的建议，包括招聘需求或项目推迟。

容量规划器 配置指南

要将此功能集成到您的环境中，请在 Openclaw Skills 框架内使用以下命令：

# 安装容量规划器技能
openclaw add capacity-planner

# 初始化您的团队配置文件
openclaw run capacity-planner --init

容量规划器 数据架构与分类体系

该技能通过利用率区间和指标的结构化框架来组织规划数据：

利用率分为三个区间：绿色（<70% 缓冲）、黄色（70-85% 紧张）和红色（>85% 倦怠）。

Capacity Planner

Plan team and infrastructure capacity before it becomes a crisis.

What It Does

Takes your current workload data — team size, utilization rates, project pipeline, seasonal patterns — and builds a forward-looking capacity model. Flags bottlenecks 4-8 weeks before they hit.

When to Use

• Sprint planning feels like guesswork
• You're not sure if you can take on a new client/project
• Hiring decisions need data, not gut feel
• Infrastructure keeps getting slammed at predictable times

How to Use

Tell the agent about your situation:

"We have 8 engineers, 3 active projects, and a new client starting in March. Can we handle it?"

The agent will:

1. Audit current load — Map people to commitments, calculate true utilization (not the number in your head)
2. Model scenarios — What happens if the new project lands? What if two people quit? What if scope grows 30%?
3. Flag risks — Identify single points of failure, overloaded roles, deadline clusters
4. Recommend actions — Hire, redistribute, defer, or say no — with numbers behind each option

Capacity Framework

Utilization Bands

Key Metrics

• Effective capacity = headcount × available hours × efficiency factor (typically 0.7-0.8)
• Demand pipeline = committed hours + probable hours (weighted by likelihood)
• Buffer ratio = (capacity - demand) / capacity — target 15-25%
• Time to constraint = weeks until demand exceeds capacity at current trajectory

Scenario Template

For each scenario, output:

• Headcount needed vs. available
• Skill gaps (specific roles/capabilities missing)
• Timeline risk (which deadlines move)
• Cost impact (overtime, contractors, lost revenue from saying no)
• Recommended action with confidence level

Output Format

CAPACITY SNAPSHOT — [Date]
━━━━━━━━━━━━━━━━━━━━━━━━━━
Team: [size] | Utilization: [%] | Buffer: [%]
Status: ??/??/??

CURRENT COMMITMENTS
- [Project A]: [X people, Y hours/week, end date]
- [Project B]: ...

PIPELINE (next 8 weeks)
- [Incoming work]: probability %, estimated load
- ...

RISKS
1. [Risk description + impact + timeframe]
2. ...

SCENARIOS
A) [Scenario]: [outcome summary]
B) [Scenario]: [outcome summary]

RECOMMENDATION
[Clear action with reasoning]

Tips

• Refresh capacity snapshots weekly during planning
• Track actual vs. predicted utilization to calibrate your efficiency factor
• Include non-project work (meetings, support, admin) — it's usually 20-30% of capacity
• Don't plan above 80% utilization. The remaining 20% isn't slack, it's where real work happens.

Go Deeper

Your capacity model is one piece of operational planning. For full business context packs covering finance, operations, and growth strategy across 10 industries:

→ AfrexAI Context Packs — $47 each, built by operators who've done the work.

→ AI Revenue Calculator — Find out where your business is leaking money (free tool).

→ Agent Setup Wizard — Get your AI agent configured for your specific business in 5 minutes.