Prepare an engineering handoff from verified notes

An engineering handoff should leave another person able to continue. This workflow prepares a document from supplied evidence; it does not inspect a repository, run builds, or coordinate coding agents.

Prepare the input

Provide the objective, change summary, exact source references if known, test outputs, unresolved issues, and ownership boundaries. Remove credentials and private logs. Mark whether each result was observed or reported by someone else.

Run the workflow

Ask for current state before history. Separate implementation, validation, integration, and deployment. Include unsuccessful attempts only when they affect the next step or preserve unique work.

Prompt to copy

Prepare a handoff from this evidence: [material].
Include objective, verified current state, changed areas,
checks actually run, unresolved work, evidence references,
and the next concrete action with its preconditions.
Distinguish source delivery from serving deployment.
Do not invent paths, commands, test results, or completion.

Review a worked example

Illustrative evidence says a patch compiled locally but was not deployed. The handoff must not say the production bug is fixed. A failed check remains unresolved even if a later note sounds optimistic. Verify source identity and every claimed check against the supplied output.

Check that evidence references identify the exact revision or run where possible. A green check from an older source does not validate a later change. Keep unfinished work and recovery locations visible without copying secrets into the handoff. The next engineer should know what can safely continue and what still needs verification.

Use it again

Update the handoff after meaningful evidence changes, not after every chat message. Have the receiving engineer confirm the next action is clear. Explore Bot for bounded preparation work or contact Golub about system-specific integration.