Aglet

Triage a Weak Agent Handoff Summary

A weak handoff forces the next person to reconstruct what was inspected and what remains open. Triage should identify the receiver's decision, compare the summary with the underlying work, and list missing context, evidence, uncertainty, and action. Bound the handoff gap before redoing the investigation.

Establish what is happening

  1. Name the receiving decision

    Write what the next engineer or reviewer must decide, change, verify, or continue. Record required scope, source revisions, time window, and constraints. Mark whether the summary answers that decision or only describes activity without a usable conclusion.

  2. Compare summary to work

    Place the summary beside notes, queries, fixtures, outputs, open questions, and owner decisions. Identify omitted evidence, unsupported compression, lost caveats, stale references, and unexplained status. Preserve exact artifact names and revisions so the gap is not reconstructed from memory.

  3. Bound continuation needs

    List the smallest context, evidence, or action needed for the receiver to proceed, plus any stop condition. Separate missing handoff detail from genuinely unfinished work. Record the owner and expected format for each open item.

What to carry forward

Return a handoff-gap brief naming the receiving decision, source work, omitted context, evidence, uncertainty, owner, and continuation boundary. Triage stops when the receiver's next action is explicit. Keep the handoff open when material claims cannot be traced to the underlying work.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow