容量规划
diegosouzapw2026-10-28查看 152复制 782
基于增长预测来预测资源需求并设计扩缩容策略
📘如何使用这个技能
- 1复制技能内容·点击上方「Copy SKILL.md」复制全部内容，或 Download 下载到本地
- 2打开你的 AI 客户端·支持 Claude Code、Trae、Cursor、ChatGPT、DeepSeek、Kimi 等任意 AI 助手
- 3粘贴为系统提示/知识文件·Claude Code：放入 .claude/skills/ 目录；普通对话：作为首条消息发送并说「请严格按这份技能文档执行」
- 4直接提出你的需求·AI 会按技能定义的工作流、格式和约束来处理，无需再解释背景
💡 提示：技能生效后，每次对话只需一句需求，AI 会按 SKILL.md 的流程执行。
SKILL.md2228 chars
--- name: Capacity Planning description: Forecast resource needs and design scaling strategies based on growth projections category: operations version: 1.0.0 triggers: - utilization-threshold - quarterly-review - scaling-strategy globs: "**/infrastructure/**,**/scaling/**" --- # Capacity Planning Skill Forecast resource needs and design scaling strategies based on growth projections. ## Trigger Conditions - Traffic spikes or utilization exceeds 75% threshold - Quarterly capacity review cycle - User invokes with "capacity plan" or "scaling strategy" ## Input Contract - **Required:** Current resource utilization metrics - **Required:** Growth forecast (user acquisition, traffic patterns) - **Optional:** Budget constraints, SLA requirements ## Output Contract - Capacity model with projections - Scaling recommendations (horizontal/vertical, auto/manual) - Cost forecast per growth scenario - Headroom analysis for failover scenarios ## Tool Permissions - **Read:** Metrics, infrastructure configs, billing data - **Write:** Capacity planning documents - **Search:** Historical usage patterns ## Execution Steps 1. Collect current utilization across compute, storage, network 2. Model demand from business metrics, not just historical extrapolation 3. Define target utilization bands (60-75%) 4. Calculate headroom for failover (lose 1 of N replicas) 5. Project costs for 3, 6, 12 month horizons 6. Recommend scaling triggers and strategies 7. Document the capacity model ## Success Criteria - Utilization targets defined per resource type - Cost projections for multiple growth scenarios - Scaling triggers calibrated for scale-up latency - Failover headroom verified ## Escalation Rules - Escalate if projected costs exceed budget by >20% - Escalate if current utilization exceeds 85% - Escalate if no scaling strategy can meet SLA targets ## Example Invocations **Input:** "Plan capacity for Black Friday (expected 5x normal traffic)" **Output:** Current: 3 pods, 45% CPU avg. For 5x: need 12 pods minimum (15 recommended for headroom). Auto-scaler trigger at 60% CPU. Pre-scale 2 hours before peak. Estimated additional cost: $2,400 for 48h burst. DB read replicas: add 2 in us-east, 1 in eu-west.