Hand off agent work
You drove an AI agent to write a Bash deployment script that's 80% there, but you've hit a wall on the rollback logic and need to hand it to a teammate on the infra team. They use a different AI assistant than you do. Write the handoff context that lets them resume effectively. What must transfer that won't carry across when they start a fresh session with their own tool?
Implement
missing_handoff_sections(note_lines: list[str]) → list[str]Examples
in
[["what_it_does=blue/green deploy plus rollback for the payments service","blocked_on=rollback cannot find the previous release tag","environment_facts=runs on the bastion, sudo needed for systemctl","constraints=BusyBox sh on the bastion, so no bashisms","verified_vs_assumed=deploy path tested on staging, rollback never run end to end"]]out[]in
[["what_it_does=deploy script, 80 percent done","constraints=","notes=ask me on slack if stuck"]]out["blocked_on","environment_facts","constraints","verified_vs_assumed"]What a strong answer looks like
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.
0:00 of about 18 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.