dangling-thread-review

name	dangling-thread-review
description	Review the conversation for threads that were started but not followed — ideas mentioned in passing, decisions deferred implicitly, tensions named but not resolved. Use when taking stock, before saving, or whenever the user wants to know what's been left on the table.

Dangling Thread Review

Read back through the conversation and surface the threads that were started but not followed.

Stance composition: Use interpretive-synthesis first to form the coherent account, then gap-reading to find what that account left out. Use diagnostic-questioning with collaborative-grounding only when the user's situated judgment determines whether a thread remains live. Use relational-continuity when carrying the result forward.

What to do

1. Read the conversation thoroughly. Not a skim. The threads you're looking for are the ones that are easy to miss — the offhand remark, the idea that got overtaken, the tension that was named and never resolved.

2. Build the coherent account first (interpretive-synthesis), then read for what it left out (gap-reading). You need the narrative of what happened in order to see what the narrative doesn't explain.

3. Categorize what you find. Not all dangling threads are equal:

   • Threads the user explicitly deferred ("let's come back to this")
   • Threads that were overtaken by momentum (the conversation moved on)
   • Ideas that surfaced without anyone recognizing their significance
   • Material the work itself produced incidentally (fragments, asides, half-formed connections)

4. Present what you found and collaborate. The user has situated knowledge about which threads are still live. Some of what you find will have been silently resolved. Some will turn out to be important. Use diagnostic-questioning to check: "I noticed you mentioned X early on and we never came back to it — is that something that matters, or was it superseded?"

When to use

• The user asks "what are we forgetting?" or "what did we leave on the table?"
• Before a session checkpoint or save
• After a significant shift in direction (threads from the old direction may be dangling)
• When the user wants to take stock without stopping

What this skill is not

• Session save (which updates the trajectory — this skill finds what the trajectory missed)
• Triage (which prioritizes known items — this skill surfaces unknown ones)
• Summary (which compresses — this skill expands, looking for what compression would lose)