Forecasting
AuraScore 83/100

Cloud Infrastructure Capacity and Cost Forecast

Forecast compute, storage, and egress demand to prevent performance bottlenecks and budget overruns.

Use this template when planning infrastructure scaling budgets ahead of product launches or traffic inflection points. It guides a systems capacity analyst to estimate resource saturation and project cloud spend.

Template

Role: Principal Cloud Capacity Architect specializing in scalable infrastructure forecasting.

Context

  • Target engineering system: {{system_name}}
  • Current monthly active users and expected growth: {{growth_metrics}}
  • Current compute and storage footprint: {{baseline_footprint}}
  • Primary cloud provider and pricing tier: {{cloud_provider}}
  • Forecast horizon window: {{forecast_window}}

Task

Produce a structured capacity forecasting analysis that predicts infrastructure saturation points, hardware resource scaling limits, and projected monthly cloud hosting expenditures for {{system_name}} across the next {{forecast_window}}.

Method

  1. Analyze {{baseline_footprint}} against the user growth vectors in {{growth_metrics}} to compute per-user compute and storage consumption rates.
  2. Model linear and peak concurrency load scenarios across {{forecast_window}}.
  3. Identify the earliest component saturation point across CPU, memory, database IOPS, and network egress.
  4. Project the required node autoscaling thresholds needed to maintain 99.99% availability.
  5. Map projected hardware utilization directly to {{cloud_provider}} pricing schedules.
  6. Evaluate reserved instance versus on-demand cost optimization scenarios.
  7. Formulate a risk mitigation strategy for unexpected load spikes above forecast thresholds.

Constraints

  • MUST express all financial projections in explicit percentage deltas and currency values relative to {{baseline_footprint}}.
  • MUST NOT recommend manual vertical scaling where horizontal autoscaling is viable.
  • MUST isolate database IOPS scaling from stateless worker node scaling.
  • Projections must account for headroom buffer of at least 25% above peak load.

Output format

  1. Executive Capacity Summary (max 150 words)
  2. Resource Saturation Timelines (Markdown table with Milestone, Resource, Saturation Date, Required Action)
  3. Projected Cost Trajectory (Monthly breakdown for {{forecast_window}})
  4. Architectural Bottleneck Risks (Top 3 prioritized risks)

Self-review

  • Confirm that every resource metric directly ties back to {{growth_metrics}}.
  • Verify that cost estimates reflect the specific pricing parameters of {{cloud_provider}}.
  • Ensure all 4 required output sections are present without placeholder content.
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

data-analytics
data-forecasting
software-engineering-debugging
capacity-planning
cloud-infrastructure
cost-forecasting