professional-communication

Structure emails, updates, and agendas with the What-Why-How framework.

9|2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/stephanj/claude-code-collections --skill professional-communication-stephanj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: professional-communication
Source: https://github.com/stephanj/claude-code-collections/tree/main/skills/professional-communication
Command: npx skills add https://github.com/stephanj/claude-code-collections --skill professional-communication-stephanj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the common struggle of crafting clear, effective, and professional communications in fast-paced software development environments, preventing misunderstandings and reducing unnecessary back-and-forth.

Core Features & Use Cases

  • Communication Frameworks: Provides the What-Why-How structure to organize emails, status updates, and meeting agendas for maximum clarity.
  • Audience Calibration: Offers strategies to translate complex technical concepts into accessible language for non-technical stakeholders.
  • Etiquette Guides: Includes best practices for team messaging, thread management, and meeting facilitation to improve team efficiency.

Quick Start

Use the professional-communication skill to draft a status update email for your current project using the What-Why-How framework.

Frequently Asked Questions about professional-communication

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a professional status update email for a software project?

A professional status update email uses the What-Why-How communication framework to structure project information for maximum clarity. This approach organizes details by explaining what the status is, why it matters, and how to proceed.

What's the best way to translate technical jargon for non-technical stakeholders?

Translating technical jargon requires audience calibration strategies to convert complex software development concepts into accessible language. This ensures non-technical stakeholders clearly understand project updates and technical constraints.

How does team messaging etiquette improve software development communication?

Team messaging etiquette improves communication by applying best practices for thread management and channel organization. This reduces unnecessary back-and-forth, prevents misunderstandings, and increases team efficiency in fast-paced environments.

How do I facilitate a meeting agenda for a development team?

Facilitating a development team meeting requires structured communication frameworks like What-Why-How to organize the agenda. This framework ensures meetings remain concise, audience-appropriate, and focused on actionable outcomes.

Can I use these communication frameworks for both written and verbal team interactions?

These communication frameworks apply to both written documentation and verbal interactions within software teams. They provide structured best practices for email composition, team messaging, and meeting facilitation across diverse audiences.