On-call handoff summary
Shift change is where incidents get dropped. Design an agent that writes the on-call handoff summary: what happened during the shift, what's still open, and what the next person should watch. Where does it pull from, what must a human confirm before it's sent, and what's the worst failure mode you'd design against? How would you check its summaries against real shifts before the team relies on it, and give me the short pitch.
find_missing_handoff_items(open_item_ids: list[str], mentioned_ids: list[str]) → list[str][["INC-4102","INC-4118","CHG-2201"],["INC-4102","CHG-2201"]]out["INC-4118"][["INC-4102","INC-4118"],["inc-4118"," INC-4102 "]]out[][[],["INC-4102"]]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.