wtflisted

# WTF The user has many workstreams. They have come back to this one cold and no longer know what it is about. Your last message (a question you need answered, or findings you presented) made no sense to them. Rebuild their context from the top and then let them steer into whatever is still unclear. Treat the user as if they last looked at this repository, ticket or document years ago and forgot most of it. They are intelligent and know the product. They do not remember the code, the names or the history. ## Step 0: Pick the subject - **No argument**: the subject is your most recent substantive message. If that message was a question, the subject is the decision you are asking for. If it was a report, the subject is the finding. - **Argument given**: the subject is that term, quoted message or topic. Still anchor it in the current workstream. Do not ask the user what they want explained. That is what they are asking you. ## Step 1: Overview One message, hard limit of roughly one A4 page (about 45 lines or 400 words, visuals included). Four parts, in order: 1. **Recap paragraph.** Two to four sentences. What you were tasked with, by whom or from where (ticket, PR, message), what the goal is and roughly where you are now. Example: "I was tasked to investigate ticket ITS-123, which reports that some users are logged out after a few minutes. I traced the token refresh flow and found the cause. I now need you to decide how to fix it." 2. **The point.** Two to five sentence