Handoff mid-refactor to teammate
You've spent two hours driving an AI agent through a half-finished refactor of a JavaScript auth module, and you're going on PTO tomorrow. A teammate will pick it up and continue the AI-assisted work. Write the handoff so they (and their agent) can continue without re-discovering everything. What context must you capture that lives in your head and the chat history but NOT in the code?
Implement
missing_handoff_sections(note_lines: list[str]) → list[str]Examples
in
[["state: token refresh is done, the session shim is stubbed","decisions: kept validateToken as a shim, three callers still use it","next: migrate the third caller, then delete the shim"]]out["rejected","verification"]in
[["state: half of the auth module is refactored","decisions: cookie format is load-bearing for mobile, do not touch it","rejected: tried moving refresh into middleware, broke the logout path","verification: unit tests pass, the e2e logout test is known-failing","next: port callers of validateToken one at a time"]]out[]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 20 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.