Capacity Planning
Forecast resource needs and design scaling strategies based on growth projections
Best use case
Capacity Planning is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Forecast resource needs and design scaling strategies based on growth projections
Teams using Capacity Planning should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/capacity-planning/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Capacity Planning Compares
| Feature / Agent | Capacity Planning | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Forecast resource needs and design scaling strategies based on growth projections
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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.
Related Skills
agile-planning
Generate agile release plans with sprints and roadmaps using unique sprint codes. Use when creating sprint schedules, product roadmaps, release planning, or when user mentions agile planning, sprints, roadmap, or release plans.
implementation-planning
Use when you have specifications or requirements for multi-step implementation tasks requiring comprehensive documentation for handoff
planning-with-files
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.
dev-workflow-planning
Structured development workflows using /brainstorm, /write-plan, and /execute-plan patterns. Transform ad-hoc conversations into systematic project execution with hypothesis-driven planning, incremental implementation, and progress tracking.
concise-planning
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
architecture-planning
Create detailed architecture plans with decision records and risk assessments. Use when planning significant features or system changes.
architectural-planning
Create detailed technical plans and implementation roadmaps by analyzing project architecture and designing solutions that integrate seamlessly with existing patterns. Use when designing features, planning integrations, making architectural decisions. Triggers: 'plan', 'design', 'architecture', 'approach', 'how should I', 'best way', 'integrate', '계획', '설계', '아키텍처', '접근법', '어떻게 해야', '가장 좋은 방법', '통합', '마이그레이션', working with multi-module features, system boundaries, complex migrations.
u04425-experiment-design-for-nutrition-and-meal-planning
Operate the "Experiment design for nutrition and meal planning" capability in production for nutrition and meal planning workflows. Use when mission execution explicitly requires this capability and outcomes must be reproducible, policy-gated, and handoff-ready.
accessibility-planning
Plan accessibility compliance - WCAG 2.2, Section 508, EN 301 549, inclusive design principles, audit planning, and remediation strategies.
planning-phase
Generates implementation plans with code reuse analysis, architecture design, and complexity estimation during the /plan phase. Use when planning feature implementation, analyzing code reuse opportunities, or designing system architecture after specification phase completes. Integrates with 8 project documentation files for constraint extraction. (project)
todo-task-planning
Execute task planning based on the specified file and manage questions[/todo-task-planning file_path --pr --branch branch_name]
inventory-demand-planning
Codified expertise for demand forecasting, safety stock optimisation, replenishment planning, and promotional lift estimation at multi-location retailers.