Demo environment manager
Sales engineers lose hours babysitting demo environments — spinning them up, loading sample data, resetting after every call. Design an agent that manages the demo fleet for them. Which infrastructure permissions does it actually need, which does it absolutely not get, and how do you make it structurally impossible for it to touch anything that isn't a demo? How would you verify it's reliable enough to trust ten minutes before a customer call, and what's your pitch to the sales-engineering manager?
decide_fleet_actions(accounts: list[str], actions: list[str], ages_days: list[int], max_age_days: int) → list[str][["demo-sandbox","demo-sandbox","prod-us-east"],["create","destroy","reset"],[0,9,2],7]out["allow","confirm","deny"][["demo-sandbox"],["modify-template"],[1],7]out["deny"][[],[],[],7]out[]Turn the fuzzy goal into a bounded agent task. Say what the agent reads, what it may do on its own versus draft for a human, and what it must never touch. Then earn the trust: how you’d verify it before rollout, and the pitch (the problem, what you built, why it matters).
Agent build: design the agent in plain language (or narrate it). The coach grades the decomposition, the guardrails, the verification plan, and the pitch.