CI failure triage agent
Your team's CI pipeline fails dozens of times a day, and engineers waste hours figuring out whether a red build is their fault, infrastructure, or a flaky test. Design an agent that triages CI failures: what signals does it read, what actions can it take on its own — say, rerunning a job — and when must it page a human instead? Then tell me how you'd verify it's trustworthy before rollout, and give me the thirty-second pitch you'd make to your platform lead.
triage_ci_failure(flaky_fingerprint: bool, infra_degraded: bool, touches_changed_files: bool, confidence: float, reruns_used: int) → str[true,false,false,0.97,0]out"rerun"[false,true,true,0.9,0]out"page_oncall"[false,false,true,0.85,0]out"notify_author"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.