Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
Forecast infrastructure resource needs (compute, storage, network). Model growth scenarios and utilization targets. Use when planning infrastructure investments or optimizing costs.
npx claudepluginhub sethdford/claude-skills --plugin architect-infrastructure-designHow this skill is triggered — by the user, by Claude, or both
Slash command
/infrastructure-design:capacity-planningThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Forecast resource needs and plan infrastructure to meet demand while optimizing costs.
Analyzes CPU, memory, storage, network utilization; forecasts growth trends; recommends scaling strategies with cost estimates. Useful for infrastructure capacity planning and bottleneck identification.
Produces a structured capacity planning document for a service covering traffic forecasts, resource requirements, scaling strategy, and cost projections.
Provides capacity planning: estimates traffic (DAU to QPS), sizes CPU/memory/network/storage, models growth/peaks, calculates infrastructure runway, correlates load tests with CI/CD.
Share bugs, ideas, or general feedback.
Forecast resource needs and plan infrastructure to meet demand while optimizing costs.
You are planning infrastructure capacity. Model growth, forecast peak load, size infrastructure for headroom. Read historical metrics, growth trends, and business projections.
Based on capacity planning and performance modeling:
Establish Baseline: Measure current usage (CPU, memory, storage, network bandwidth). Peak vs average. Growth rate over past 6-12 months.
Project Growth: Based on growth rate and business projections. Linear extrapolation for stable growth. Exponential model for hypergrowth startups. Add margin for uncertainty.
Calculate Required Capacity: For peak load + 20% headroom, how many servers needed? At 70% CPU utilization per server, peak_load / 0.7 = servers needed.
Model Scenarios: Best case (fast growth, more servers). Worst case (slow growth, fewer servers). Plan investment for mid-case; be ready to scale up/down.
Plan Upgrades: When do you need additional capacity? In 6 months? Plan lead time for procurement, setup, migration. Use auto-scaling to smooth spikes; only add permanent capacity when needed.