Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mohitagw15856/capacity-planning
Produce a capacity planning document for a service covering traffic forecasts, resource requirements, and scaling strategy.
Passed 18 of 22 test cases with the skill, and 10 of 22 without it.
and 8 more in the full report
8 fixed10 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
What structural metadata block must appear at the top of a formal capacity plan document before Section 1 Executive Summary?
| Checked | Without skill | With skill |
|---|---|---|
| Includes Planning horizon in the document header block. | Passed | Passed |
| Includes Review cadence in the document header block. | Missed | Passed |
The instructions your model reads when the skill loads.
Produce a complete capacity planning document for a service. Capacity planning is not about predicting the future exactly — it is about understanding current headroom, modelling growth, and ensuring the team takes infrastructure action before a constraint becomes an incident.
A good capacity plan answers: what is running out first, how long before it runs out, what does it cost to fix it, and who decides when to act.
Ask for these if not already provided:
Service: [Name] | Team: [Team name] Author: [Name] | Last updated: [Date] Planning horizon: [12 months — [Month Year] to [Month Year]] Review cadence: [Quarterly]
[3–5 sentences covering: current state, the most critical capacity constraint, the timeline before it becomes a risk, the recommended action, and the cost implication. Written for an engineering manager or VP who needs the key facts without reading the full document.]
Critical finding: [e.g. "The database connection pool will reach 90% utilisation within 6 weeks at current growth. Without action, this will cause request queueing and latency spikes under normal traffic."]
Recommended immediate action: [e.g. "Increase connection pool limit and add a read replica within the next 2 weeks."]
Estimated cost impact: [e.g. "Recommended changes add ~$[X]/month to infrastructure spend."]
test cases passed, vs 10 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.