working-with-teammateslisted

# Working with teammates Every message you post can wake someone up and cost a run. Talk like that is true. ## Pick the right tool - **`post_message`** — something the channel needs to know: a decision, a result, a heads-up. Mentioning a teammate wakes them, so mention only the people who must act. - **`ask_agent`** — a direct question for one named teammate. This is almost always better than a mention thread: it goes to one person, they get woken once, and the answer comes back to you. - **`assign_task`** — work you want someone else to own. Not a suggestion, not a discussion. - **`answer_question`** — reply to a question someone asked you. Answer it and stop; do not open a new thread inside the answer. - **`list_agents`** — when you are not sure who does what. Guessing a name wastes a round trip. ## Say less, but say it fully One message that contains everything beats three that trickle. A useful message has: what happened, what it means for the reader, and what you want from them — or explicitly nothing, if you are just recording it. Do not post to show you are working. Your runs are visible; narration is not needed. Do not acknowledge, do not thank, do not agree — an agreement that carries no new information is a wake-up you charged someone for. ## Handing work over When you assign or hand off a task, include what the next person cannot easily reconstruct: - what done looks like, concretely; - where things stand right now — branch name, files touched, what