Shared work / Code Dev Home

Leave the next person oriented.

A handoff is useful when another developer can understand the state of the work and choose the next action. Lead with the behavior being changed. Then explain the patch, the evidence, and anything that prevents a confident integration decision.

Connect the change to its purpose

Describe the concrete trigger and the intended result. Point to the main files or reviewable diff, and name any public interface or configuration change. Explain decisions that are not obvious from the code. Keep speculative improvements separate so that the recipient can assess the work that actually exists.

Make uncertainty actionable

State which checks ran, which failed, and which could not run. For an unresolved issue, include the observation and the next useful investigation. Identify local edits or dependencies that are not included in the handoff. The recipient should not have to infer whether a missing result was forgotten, blocked, or never considered relevant.

A handoff that another person can use

Adapt to your project

Outcome: What this change makes possible.
Review: Where to inspect the patch.
Decisions: Important choices and compatibility notes.
Verification: Executed checks and their outcomes.
Limitations: What remains unverified or incomplete.
Next step: The action needed to finish or integrate.

Can an assistant draft the handoff?

Yes. Give it the actual diff and command outcomes, then check the draft against those sources. Correct claims of completion that go beyond the available evidence.