Produce a handoff another engineer can trust.
1. Completion criteria
Stop when acceptance criteria and relevant checks pass, not when the agent has generated a large amount of code. Additional cleanup requires a concrete reason.
2. Known limitations
Distinguish tested behavior from assumptions and pre-existing failures. Do not report a full release build if only a module compile was run.
3. Learning from revisions
Record recurring review failures and improve project guidance narrowly. Avoid accumulating contradictory instructions after every isolated issue.
Worked scenario
The final handoff states that debug behavior was verified on one emulator and release signing was outside the task.
Apply it
Write a concise change description with problem, behavior, validation and remaining limitations.
Check your understanding
A reviewer can assess the patch without reading the agent conversation. Explain the decision and show evidence from your implementation or design. If you cannot demonstrate it yet, revisit the relevant section before continuing.