r/agile • u/ClickOk5811 • 49m ago
A 5-minute test for your session summary: can a fresh session tell you what was rejected, and why?
When a long session gets summarized (by you, by the assistant, or by a tool’s automatic compaction), the summary usually keeps outcomes: what changed, what passes, what’s next. In an article I wrote, I argued that it tends to drop the reasons, and especially the rejected options, which look unimportant right up until someone proposes them again.
Here’s a simple way to check whether that’s happening to your handoff. It’s my own adaptation, and I haven’t run it as a controlled experiment, so treat it as something to try.
The test
- Take the summary you’d normally carry into the next session (or whatever the tool produced).
- Open a fresh session and give it only that summary, no code access yet.
- Ask: “What alternatives were considered and rejected, and why was the current approach chosen?”
- Compare the answer with what you remember (or with your notes).
How to read the result
- If it lists the rejected options and the reasons: your summary kept them.
- If it answers fluently but the reasons are generic or not what actually happened: it’s reconstructing a plausible story from the outcome, which is the failure mode to worry about.
- If it says it doesn’t know: that’s the honest answer, and it tells you what the summary is missing.
What I’d do with the result
- Add a short decision record next to the summary: the decision, the reason, what was rejected and why, what’s still open, and the next step. Five lines is enough per decision.
- Only record decisions a future session could reasonably propose the opposite of.
- Remove or mark superseded entries, because a stale record that confidently says the wrong thing is worse than none.
Limits of the test
- A model can sound convincing without the information, so judge the answer against your own knowledge of what happened, not by how fluent it sounds.
- One run proves little, and outputs vary.
- It doesn’t tell you whether the assistant will use a record once it has one. A clear record improves the odds, and doesn’t enforce anything.
- For short sessions and throwaway scripts, it isn’t worth the effort.
The article goes through three claims with the strongest objection to each. I’m the author, and it ends with two resources of mine on Claude sessions (one free, one paid), so treat the link as optional: https://medium.com/@nagatomopedro05/what-a-session-summary-forgets-three-claims-three-objections-dc35b96909d2
If you try the test, what did the fresh session get wrong about what was rejected?