professional-communication

This skill provides frameworks and guidance for effective professional communication in software development contexts. Whether you're writing an email to stakeholders, crafting a team chat message, or preparing meeting agendas, these principles help you communicate clearly and build professional credibility. Core principle: Effective communication isn't about proving how much you know - it's about ensuring your message is received and understood. Use this skill when: Keywords : email, chat, teams, slack, discord, message, writing, communication, meeting, agenda, status update, report Use this universal framework to organize any professional message: Apply to : Emails, status updates, meeting talking points, technical explanations Before communicating, ask yourself: For templates : See references/email-templates.md Note: Examples use Slack terminology, but these principles apply equally to Microsoft Teams, Discord, or any team messaging platform. Instead of: Try: For more examples : See references/jargon-simplification.md Active voice is clearer, more direct, and conveys authority: After writing, ask: "So what? Why does this matter to the reader?" If you can't answer clearly, restructure your message to lead with the value/impact. Every meeting invite should include: For structures by meeting type : See references/meeting-structures.md Before sending any professional...