This article was prepared with AI using the sources below. Read those sources for their original context.
Microsoft Research describes a method called APEC for preparing summaries while a coding agent keeps working. If you are deciding how to use a coding agent on your own team, start with a narrower question. When a task takes longer than expected, can the developer pick it up without explaining the problem again?
Try the same change in two ways
Pick a small, real maintenance task with a clear definition of done. Work from the same starting point on separate branches. Try keeping the work in one session on the first branch. On the second, split it into a diagnosis and a fix. Before opening the second session, write down the intended change, decisions already made and checks still to run.
Ask the developer to keep a simple log. How long did it take to get a change that passed the agreed checks? How often did they have to restate a decision or point the agent back to a file? If you can see the usage for each run, record it alongside the time spent reviewing and correcting the change.
Check whether another person can take over
Give the handover note and branch to a colleague. Ask them to explain what they would check before merging, then compare their list with the original acceptance criteria. If the handover misses an important constraint, add that constraint to the note and repeat the exercise on the next comparable task.
Choose a rule for the next trial
If splitting the work made it easier to review or hand over, try starting a new session after the next decision point. If the extra handover took more effort than it saved, keep the session open and jot down the decisions as you go. Decide what would make you change that rule. For example, would you split a task as soon as a second developer needs to take it over?
Start this week with one issue that already has a test you can run. Save the branch, the short handover and the time log together so the team can discuss a real example at its next review.
Sources
- Microsoft Research Focus – Edition #98 ↗ · Microsoft Research
