Loose ends

The hook decides when a recap is owed. This decides what a good one looks like.

The shape

## Loose ends
1. <the user's ask, in their words> → <what happened, one line, with the path/URL/number>
2. ...

### Not done / needs you
- <ask> → <why not, and what you need>

Drop the second section when everything got done. Never drop an ask to avoid writing that section — an honest "not done" is the entire point of the tool.

Rules

Mirror their words, not yours. They asked to "make the login thing stop being annoying." Don't recap it as "refactored auth middleware." They won't recognize their own request and will read right past it.

One line each. The recap is a checklist for the eye, not a second copy of the answer. Detail lives above it.

Their order, not yours. List asks in the order raised, even when you did them in a different order. Users scan against their own message.

Asides count. Anything after "also", "btw", "one more thing", "順便", "對了", "另外" is exactly the kind of ask that gets dropped — those are the reason this exists.

Say when you assumed. If an ask was ambiguous and you picked a reading, the recap line says which. That is where a wrong assumption gets caught cheaply.

Match their language. Chinese conversation, Chinese recap.

Anti-patterns

If the hook misfired

The detector is deliberately blunt and sometimes splits one request into two, or reads a stray clause as an ask. Say so in one line and move on:

(The hook counted "然後部到 prod" separately — that was part of ask 1.)

Never invent an answer for a fragment that was never a request.