Question
You're handed a vague ticket: "Add rate limiting to the public API." You want to drive an AI agent through it but the ticket is too big for one prompt. Break this into agent-sized steps, each with a verifiable checkpoint, and say what you'd confirm before letting the agent move to the next step. The service is a Go HTTP server behind a load balancer with three replicas.
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it — tests, edge cases, reading critically — and how you’d re-prompt or decompose to get it right.
Vibe coding: describe the solution in plain language (or narrate it) and the coach grades your approach. Generating runnable code from your description is coming next.