SkillVaultskills Browse all 1,000+ skills

Reliability · Version 1.4.0 · Reviewed 2026-08-02

Capacity Forecasting Analyst

Reduce production risk in growth modeling and binding constraint with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Forecasts infrastructure capacity from growth, seasonality, and the resource that actually binds first.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools, with a raw SKILL.md fallback for every other compatible IDE or agent.

See the complete graphical installation and usage guide

What this skill helps you do

  • Growth modeling
  • Binding constraint
  • Lead time planning

How Capacity Forecasting Analyst works

You provide

Impact window, telemetry, and dependency state

It inspects

Saturation and blast radius behind growth modeling

It decides

A binding constraint plan that stabilizes before diagnosing

You verify

Detect, mitigate, and resolve times recorded separately

What it checks first

Capacity Forecasting Analyst forecasts infrastructure capacity from growth, seasonality, and the resource that actually binds first. Use it when the work involves Growth modeling, Binding constraint, Lead time planning.

  1. User-visible impact and error-budget consumption rather than component health.
  2. Saturation signals — queue depth, pool utilization, connection counts — near the onset.
  3. Whether the system recovered on its own, which indicates saturation rather than corruption.
  4. The blast radius and what boundary should have contained it.

Failure modes it recognizes

  • Retry amplification turning a partial failure into a total outage.
  • A shared dependency creating correlated failure across supposedly independent services.
  • Slow resource exhaustion invisible until a hard limit is crossed.
  • A rollback blocked by an incompatible migration.

Answers it will reject

  • Treating the trigger as the root cause, which stops the analysis before the fragility is identified.
  • Adding a runbook step where a boundary would remove the failure mode.
  • Measuring availability as a mean, which hides regional and tenant-level outages.

Decision rules it applies

  • Stabilize user impact before completing diagnosis.
  • Bound every retry with a budget, jitter, and a circuit breaker.
  • Prefer removing a failure mode over detecting it faster.

Evidence it asks for

  • Record time-to-detect, time-to-mitigate, and time-to-resolve separately.
  • Quantify impact in customer terms: failed requests, affected accounts, duration.
  • Verify recovery with the same signal that detected the failure.

The method inside

  1. Define the measured baseline and user-visible target for growth modeling.
  2. Attribute the dominant cost or latency mechanism affecting binding constraint.
  3. Rank lead time planning changes by expected impact, confidence, effort, and regression risk.
  4. Validate under representative load and retain guardrail metrics that detect a shifted bottleneck.

Deliverables

  • Growth modeling assessment
  • Binding constraint decision and action plan
  • Lead time planning verification checklist

Evidence requirements

  • User-visible symptoms and SLO impact
  • Timeline, telemetry, deploys, and dependency state
  • Current mitigations and operational constraints

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

We need a capacity plan for next year. Growth is 8 percent monthly and we have annual procurement lead times.

Expected output

With a year of lead time the binding question is which resource saturates first, and it is rarely the one you buy most of. Model each resource independently against the growth curve, and plan for the earliest saturation date rather than an average...

Boundaries and compatibility

Ideal for

  • Growth modeling: produce a decision or artifact grounded in supplied evidence.
  • Binding constraint: produce a decision or artifact grounded in supplied evidence.
  • Lead time planning: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Replacing incident command authority
  • Calling a trigger the root cause without a causal chain

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.