teams-followuplisted

# Teams Followup The user points at a message and hands it to you. You work out the answer, tell the sender you are on it, put a draft where the user can judge it from a phone, and post it yourself once they say yes. ## The loop 1. **Investigate.** Read the source message and follow what it points at - work items, pull requests, wiki pages, earlier messages in the thread. If it needs real thought, think it through before drafting anything. 2. **React 🤔 on the source** once an answer is within reach. Not when the draft is finished - earlier, while you are still working. The point is to tell the sender a human is on this, and a signal that arrives with the reply has said nothing. This is the user's own rubric; check `reference-teams-reactions.md` in their memory for what the emoji mean. 3. **Draft to the user's self chat**, one message, `format: "markdown"`. Destination comes from `reference-teams-destinations.md`. Shape below. 4. **Wait for the verdict** with the poller. A reaction approves; a reply is feedback. On approval, post the draft to the original conversation and mark the source done. On feedback, revise, resend as a new draft, re-arm. Steps 1-3 are the `teams-message` skill's drafting rules, unchanged - the critique pass, the markdown file as durable record, the humanizer. This skill adds the reacting, the waiting and the forwarding around them. ## The draft message One message, and the approval cue lives inside it: ``` <the exact t