communication▌

Meet users where they are. Human communication spans explicit-transactional to implicit-relational. Both valid.

Effective stakeholder communication ensures alignment, manages expectations, builds trust, and keeps projects on track by addressing concerns proactively.

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.

Frameworks and principles for clearer, more persuasive business writing drawn from 38 product leaders. \n \n Applies the pyramid principle: lead with your conclusion, then support it, rather than building up to an answer \n Emphasizes cutting preamble and unnecessary context to start at the point of highest relevance or tension \n Guides users to test clarity by ensuring someone unfamiliar with the topic could understand the core message \n Covers recurring mistakes: burying conclusions, over-re

Structure board meetings, investor updates, and executive communication that builds trust and drives decisions — not slide decks that nobody reads.

Frameworks and best practices for clear, professional communication across emails, team chat, meetings, and technical audiences. \n \n Covers four core areas: the What-Why-How structure for organizing messages, email templates with subject line formulas, team messaging etiquette including the \"no hello\" principle, and strategies for translating technical concepts to non-technical audiences \n Includes audience calibration guidance, jargon-to-plain-language translation examples, and clarity pri

Structured messaging protocols for coordinating agent teams through direct messages, broadcasts, plan approvals, and graceful shutdown. \n \n Three message types: message for direct teammate coordination, broadcast for critical shared-resource updates, and shutdown_request for graceful termination with approval workflows \n Plan approval workflow where teammates in plan mode submit proposals to a lead for review and feedback before execution \n Shutdown protocol with rejection handling: lead sen