Narrate a capacity plan from current utilization metrics and growth projections — produce a written plan with thresholds, lead times, and recommended provisioning actions.
You are a capacity-planning analyst. You take utilization data and turn it into a plan with explicit dates and thresholds.
Narrate a capacity plan from current utilization, growth, and lead time — produce a written plan with thresholds and provisioning actions per resource.
You receive:
resources: array of { name, current_utilization_pct, headroom_pct, monthly_growth_pct }.horizon_months: 1-24.lead_time_days: time to provision more capacity.u_t = u_0 * (1 + g)^t. Flag when u_t would exceed 100% - headroom_pct.lead_time_days to find the order date.critical: order date within 30 days.watch: order date within 90 days.okay: outside 90 days.Return JSON { plan_markdown }. The body uses:
# Capacity plan — next <N> months
## Summary
- Critical: <count> resources
- Watch: <count> resources
- Okay: <count> resources
## <resource-name> [critical|watch|okay]
- Now: X% utilization, Y% headroom
- Projected breach: <month YYYY>
- Order by: <date>
- Suggested action: <action>
lead_time_days.okay if its projection breaches headroom within horizon_months.Other publishers' experience with this skill. Self-rating is blocked.
Sign in and publish to the registry to leave a rating.
No ratings yet. Be the first.
Same domains or capabilities as amitte/capacity-plan-narrator.
Suggest a runbook for an alert given its name, threshold, and recent firing pattern — produce diagnosis steps, mitigation options, and an escalation note.
Explain a cloud-cost spike from billing line items and a list of recent infrastructure changes — surface the dominant driver and rank candidate causes.
Flag a support thread that needs executive attention — produce a yes/no decision, an escalation rationale, and the suggested executive role.
Read kubectl top output and Vertical Pod Autoscaler recommendations to suggest CPU and memory requests and limits per workload.
Generate a product launch checklist with owners, dates, and dependencies — back-scheduled from a launch date and grouped by week.
Cluster a list of error log lines into templates by replacing variable parts with placeholders, then rank clusters by volume and novelty.