CP
Capacity Planning
🔵 Stable🕐 updated 2026-06-08
🔷 SkillSpec L3
pm-engineering
Produce a capacity planning document for a service covering traffic forecasts, resource requirements, and scaling strategy. Use when asked to plan infrastructure capacity, forecast resource needs, model traffic growth, define scaling strategy, or produce a capacity review for a service. Produces a structured capacity plan covering current baseline metrics, growth projections, resource requirements per tier, scaling strategy, cost projections, capacity triggers, and an infrastructure action roadmap.
What to give it
▸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
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓Every resource has a quantified current utilisation and a projected months-to-ceiling — no hand-waving
✓The most critical constraint is called out in the executive summary with a specific timeline
✓Growth projections state their assumptions and confidence level — not presented as certainties
✓Capacity triggers define amber/red thresholds and name who acts at each level
✓Cost projections include unit economics, not just absolute totals
✓The infrastructure roadmap has named owners and effort estimates — not just a wish list
✓Auto-scaling configuration includes both scale-out AND scale-in triggers, and a min/max range
✓Actions are ordered by urgency — immediate items are genuinely immediate, not backlog filler
⚠️ What it refuses to do
Do not set capacity trigger thresholds without knowing the baseline — a "CPU > 70%" alert is meaningless if you don't know what normal looks like
Do not plan only for average traffic — capacity plans that don't model peak load will result in incidents during the events that matter most
Do not conflate vertical and horizontal scaling — adding more app servers without addressing database connection limits will not resolve the constraint
Do not present growth projections as certainties — all forecasts have uncertainty; state the confidence level and provide a conservative and optimistic scenario
Do not defer action items without a named owner and a specific date — a roadmap with no owners is a wish list
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcpStart with
Related skills
🔌 Embed this skill
Drop this on your blog, docs, or site — it renders a "Run this skill" card:
<div data-pm-skill="capacity-planning"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>💬 Discussion
Capacity Planning is one of 1078 open-source professional AI agent skills — all SkillSpec L3.
Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog