Capacity Planning Skill

Produce a complete capacity planning document for a service. Capacity planning is not about predicting the future exactly — it is about understanding current headroom, modelling growth, and ensuring the team takes infrastructure action before a constraint becomes an incident.

A good capacity plan answers: what is running out first, how long before it runs out, what does it cost to fix it, and who decides when to act.

Required Inputs

Ask for these if not already provided:

• Service name and description — what the service does and who depends on it
• Current traffic and usage metrics — requests per second (or per day), active users, data volume — whatever units are most natural for this service
• Current resource utilisation — CPU %, memory %, disk usage, connection pool utilisation, DB query throughput
• Growth rate or projections — historical growth rate, or known upcoming events (product launch, sales cycle, seasonal peak)
• Tech stack and infrastructure — cloud provider, compute type (VMs, containers, serverless), database, caching layer, CDN
• Cost constraints — current infrastructure spend, acceptable cost ceiling, or target cost per unit of traffic

Output Format