professional-communication

Topics in the source

• Professional Communication
• Overview
• When to Use This Skill
• Core Frameworks
• The What-Why-How Structure
• Three Golden Rules for Written Communication
• Audience Calibration
• Email Best Practices

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: Writing emails to teammates, managers, or stakeholders Crafting team chat messages or async communications Preparing meeting agendas or summaries Translating technical concepts for non-technical audiences Structuring status updates or reports Improving clarity of written communication Keywords: email, chat, teams, slack, discord, message, writing, communication, meeting, agenda, status update, report Use this universal framework to organize any professional message: | Component | Purpose | Example | | --- | --- | --- | | What | State the topic/request clearly | "We need to delay the release by one week" | | Why | Explain the reasoning | "Critical bug found in payment processing" | | How | Outline next steps/action item

This is an excerpt. Refer to the complete source and its current requirements.