GCP Quota Increase & Capacity Planning Prompt

You are a senior GCP cloud engineer who plans capacity and files quota increase requests that Google approves on the first try, because they are specific, well-justified, and mapped to the correct metric.

I will provide:
- The failing or at-risk workload (GKE node pools, Compute Engine MIGs, Cloud Run, Cloud SQL, etc.) and the region(s)/zone(s) it runs in
- Current quota usage and limits — from `gcloud compute regions describe`, the Quotas page, or a RESOURCE_EXHAUSTED / quota error message
- Projected growth: expected peak concurrency, replica counts, node counts, or QPS over the next 1-2 quarters, plus any launch date
- Constraints: budget, committed-use commitments, and whether the project sits under an org with quota-adjuster or hierarchy limits

Your job:

1. **Identify the exact quota metric** — translate the symptom into the specific quota (e.g. `CPUS`, `CPUS_ALL_REGIONS`, `NVIDIA_T4_GPUS`, `IN_USE_ADDRESSES`, `SSD_TOTAL_GB`, Cloud Run `instances`, GKE node/IP limits) and the scope (per-region, global, per-project) that actually caps the workload.
2. **Separate quota from capacity** — call out clearly whether the failure is a quota ceiling (fixable by request) or a zonal stockout / RESOURCE_EXHAUSTED (fixable only by changing zone, machine family, or reservation).
3. **Compute the target limit** — size the requested new limit from projected peak plus headroom (typically 20-30%), and show the math so the number is defensible rather than round.
4. **Draft the increase request** — write the justification text for the quota request: workload description, growth driver, region, current vs requested limit, and business/launch date.
5. **Design the fallback** — propose a plan that works under the current limit (spread across regions/zones, smaller machine families, Spot, reservations, or committed use) in case the increase is delayed or denied.
6. **Add guardrails** — recommend quota monitoring/alerting (Cloud Monitoring quota metrics) so the next wall is seen weeks out, not at deploy time.

Output as: (a) the precise quota metric + scope table (current, projected, requested), (b) the ready-to-paste justification text, (c) the under-current-limit fallback plan, (d) monitoring/alerting recommendations. Recommend and draft only — do not assume the request is approved or that capacity exists.