professional-communication

Provide frameworks and templates for clear professional communication.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/program-the-brain-not-the-heartbeat/dotfiles --skill professional-communication-program-the-brain-not-the-heartbeat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: professional-communication
Source: https://github.com/program-the-brain-not-the-heartbeat/dotfiles/tree/main/config/claude/skills/professional-communication
Command: npx skills add https://github.com/program-the-brain-not-the-heartbeat/dotfiles --skill professional-communication-program-the-brain-not-the-heartbeat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Clear, effective professional communication is critical in software teams. This guide provides frameworks, templates, and practical guidance to craft concise emails, well-structured messages, and productive meeting notes, reducing ambiguity and accelerating collaboration.

Core Features & Use Cases

  • Email best practices and templates for common scenarios (status updates, requests, escalations)
  • Team messaging etiquette and async communication strategies
  • Meeting preparation, structure, and summaries to drive outcomes
  • Technical vs non-technical translation for cross-functional work
  • Clarity and tone guidance for impactful writing in engineering contexts

Quick Start

Ask me to draft a concise status update using the What-Why-How framework to align your team.

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 email status update for a software development team?

Structure your status update using the What-Why-How framework to align your team. This method provides templates for concise emails and cross-functional updates, reducing ambiguity and accelerating collaboration in software development.

What is the best way to structure meeting agendas and notes for engineering teams?

The best way to structure meeting notes is by applying frameworks for meeting preparation and summaries that drive outcomes. This ensures productive technical meetings with clear, actionable next steps for the engineering team.

How do I translate technical updates for non-technical cross-functional stakeholders?

Translate technical updates for non-technical stakeholders using audience-calibration guidance. This helps craft clear messages by adjusting technical jargon into accessible language, ensuring cross-functional teams understand the software development context.

Can I use templates for team messaging and async communication strategies?

Yes, you can use templates for team messaging and async communication strategies. These templates provide practical guidance for team messaging etiquette, ensuring well-structured messages that maintain clarity and tone in engineering contexts.

How do I communicate an escalation email to reduce ambiguity in software projects?

Communicate an escalation email using best practices and templates for common scenarios. This provides frameworks to craft concise, actionable messages with appropriate tone, reducing ambiguity and accelerating collaboration during project escalations.