Reduce cloud costs and right-size capacity
Finds waste and optimization opportunities in your cloud spend.
The prompt
Role: Act as a platform engineer reviewing cloud cost and capacity.
Context: Cost breakdown by service / team / environment: [COST_DATA]. Utilisation data (CPU, memory, storage, network) for the main workloads: [UTILISATION]. Commitments in place (reserved / savings plans): [COMMITMENTS]. Growth expectations: [GROWTH]. Reliability / performance constraints that limit changes: [CONSTRAINTS].
Task: Produce: (1) where cost concentrates and the trend; (2) waste - idle/underused resources, oversized instances, orphaned storage, inefficient data transfer, non-prod running out of hours; (3) right-sizing and architecture opportunities with estimated saving and the risk/effort of each; (4) commitment coverage recommendations given the growth expectation; (5) a phased plan starting with zero-risk changes, with a rollback note per change.
Format: Sections: Cost concentration | Waste findings (table) | Right-sizing opportunities (table: Change | Est. saving | Risk | Effort) | Commitment coverage | Phased plan. ~500 words.
Verification: Base every saving estimate on the utilisation data provided and state the assumption; flag changes that could affect the reliability/performance constraints.
Validation: Pressure-test the top 3 changes against a peak-load day: would right-sizing there cause a problem? Keep headroom and revise the estimate.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Software Development prompts
What to fill in
- COST_DATA
- UTILISATION
- COMMITMENTS
- GROWTH
- CONSTRAINTS
How this prompt is built
This prompt follows the RCTFVV structure (Role, Context, Task, Format, Verification, Validation). RCTFVV extends RCTF with two checking steps. Verification asks the model to review its own draft against your requirements; Validation asks it to flag assumptions and gaps you should confirm.
Related prompts
- Review my code for bugs, security, and qualityA thorough code review with prioritized findings and suggested fixes.
- Create a test plan and test casesA risk-based test strategy with test cases for functional, integration, and end-to-end testing.
- Triage defects and assess regression riskPrioritizes bugs by severity and impact and flags regression risk.
- Write an incident postmortem and runbookA blameless postmortem with timeline, root cause, actions, and a runbook update.