← Blog
Week of

Retrospective reconstruction · Published · Weekly archive

Send the result, not a tour of the session

A task can take hours and still deserve a short handoff.

Field NotesRetrospective

Retrospective field note for 2025-12-08. Reconstructed in November 2026 from dated sources, not originally published on the archive date.

A task can take hours and still deserve a short handoff.

After the late-November Opus 4.5 release, the question for longer workflows is what reaches the person at the end. They shouldn’t have to reconstruct the session to work out whether the job finished.

Lead with the result. Then give them the thing: the document, the pull request, the working page, or the service confirmation. “I’ve updated some files” isn’t much use if they don’t know where to look.

Say what was checked. A successful build doesn’t establish that every behaviour is unchanged, so don’t turn it into “no regressions”. If the page was inspected on desktop but not mobile, that’s a short and useful limitation.

Record decisions that will matter later. Why was a dependency rejected? What condition makes a workaround removable? Keep that detail with the project rather than burying it in a closing message nobody will find again.

The handoff isn’t a performance review for the agent. It doesn’t need to justify every minute spent. It needs to let the person inspect the outcome and move on. If something is still blocked, name that first rather than hiding it after a paragraph about progress.

Sources

All posts Work with me