Skip to main content
Back to Prompt Library
Build the complete application

Implementation brief

Inspect the original prompt language first, then copy or adapt it once you know how it fits your workflow.

Linked challenge: Build a Cloud Resource Savings Planner

Format
Code-aware
Lines
60
Sections
11
Linked challenge
Build a Cloud Resource Savings Planner

Prompt source

Original prompt text with formatting preserved for inspection.

60 lines
11 sections
No variables
1 code block
## Who Uses It
A cloud operations team reviewing avoidable infrastructure spending.

## What You Will Build
Build an agent that analyzes resource inventory, usage, cost, and ownership to propose infrastructure savings. Show the evidence, capacity impact, and review steps for every proposed change.

## Inputs
- Resource inventory
- Usage and cost exports
- Ownership and capacity policies

## Workflow
1. Join resource, cost, and usage records.
2. Identify idle or oversized resources.
3. Check ownership, recovery reservations, and capacity limits.
4. Produce a prioritized change plan with estimated savings.

## Interface
A savings dashboard with resource-level evidence, exclusions, estimated monthly savings, and a change-plan export.

## Working Demo
Recommend disk-A for review, preserve disk-B and node-C, and explain the supported monthly saving of 20.

## Deliverables
- A working local application with the specified review interface.
- Source code, dependency lockfile, and setup commands.
- A recorded end-to-end demo using the supplied starter data.
- Example outputs, action logs, and automated tests.

## Starter Data
These fictional records are a small development fixture, not a production dataset. Implement the mock services described in the brief.

```json
{
  "request": "Find monthly savings without affecting recovery capacity.",
  "resources": [
    {
      "id": "disk-A",
      "monthly_cost": 20,
      "attached": false,
      "owner": "ops",
      "restore_reserved": false
    },
    {
      "id": "disk-B",
      "monthly_cost": 30,
      "attached": false,
      "owner": "ops",
      "restore_reserved": true
    },
    {
      "id": "node-C",
      "monthly_cost": 100,
      "peak_utilization": 85,
      "minimum_headroom_percent": 15
    }
  ]
}
```

## Constraints
Read exported data and generate proposed changes only. Never apply infrastructure changes.
Choose an available model that supports your implementation. Record its identifier and version.

## Evaluation
Review the complete application, not only the starter-case answers.
- Savings total is 20 for this bundle.
- The recovery disk is excluded.
- The plan contains no executed deletion.
Add one normal case, one incomplete-input case, and one failure-recovery case.

Adaptation plan

Keep the source stable, then change the prompt in a predictable order so the next run is easier to evaluate.

Keep stable

Preserve the source structure until you know which part of the prompt is actually driving the result quality.

Tune next

Change domain facts, examples, and tool context first before you rewrite the instruction scaffold.

Verify after

Validate one failure mode at a time so prompt changes stay attributable instead of getting noisy.