By name: async-communication-etiquette description: Use this skill when writing messages in async channels (Slack, GitHub issues, email threads) where the reader may not have context and cannot ask follow-up questions immediately. category: communication
Async Communication Etiquette
Make messages self-contained:
- Include enough context that the reader doesn't need to chase down previous messages.
- Link to relevant issues, PRs, docs, or code rather than assuming the reader has them open.
Structure for complex messages:
- Context: 1–2 sentences on the situation.
- Problem/question: What specifically do you need?
- Options considered (for decisions): What alternatives exist?
- Deadline: By when do you need a response?
Anti-patterns:
Hey, got a sec?without stating the topic (forces a round trip).- Tagging @channel for non-urgent messages.