written-communication

Draft audience-calibrated written messages using a Prepare/Write Simply/Garbage Collector structure.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/imsus/cto --skill written-communication-imsus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: written-communication
Source: https://github.com/imsus/cto/tree/main/.agents/skills/written-communication
Command: npx skills add https://github.com/imsus/cto --skill written-communication-imsus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Written communication fails when the sender’s intent gets lost, misunderstood, or repeated publicly; this Skill helps engineering managers produce clear, audience-calibrated messages that land well in async channels and stakeholder settings.

Core Features & Use Cases

  • 3-Step Writing Framework (Prepare / Write Simply / Run a Garbage Collector) to draft concise messages with the right intent, audience calibration, and scannable structure.
  • Async Re-Explanation Trap guidance to handle “as I already said” situations without humiliating the recipient or damaging relationships.
  • Compression/Decompression model to diagnose why messages are misunderstood by balancing missing context vs. over-explaining.
  • When Stakes Are High prompting lightweight pre-send review to reduce high-impact misunderstandings.
  • Use for drafting: messages, announcements, stakeholder updates, and team-wide communication; avoid for verbal feedback or difficult conversations (use the referenced skills instead).

Quick Start

Use the written-communication skill to draft a Slack announcement about a process change for engineering managers.

Frequently Asked Questions about written-communication

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

FAQPage Schema
How do I write Slack announcements that engineering managers actually understand?▼

To write stakeholder updates that are understood, calibrate the message to the audience first, draft it simply, and remove excess information. This balances missing context against over-explaining to prevent misunderstood outcomes.

What is the best way to draft stakeholder updates for asynchronous channels?▼

The best way to draft asynchronous stakeholder updates is audience calibration. Apply a Prepare, Write Simply, and Garbage Collector structure to compress information correctly, ensuring the intent lands without over-explaining.

How do I re-explain a missed message asynchronously without humiliating the recipient?▼

To re-explain a missed message without humiliating the recipient, avoid the "as I already said" trap. Frame the async clarification neutrally by providing the missing context again, treating the misunderstanding as a compression issue rather than a recipient failure.

Why does my written communication get misunderstood when I post team updates?▼

Your written communication gets misunderstood due to a compression and decompression mismatch. If recipients lack context or you over-explain, the intent gets lost; diagnosing this balance helps restructure the message for clarity.

Can I use this written communication approach for difficult conversations or verbal feedback?▼

You cannot use this approach for difficult conversations or verbal feedback. It is specifically designed for drafting written messages, stakeholder updates, and async clarifications; referenced skills should be used for verbal scenarios instead.

Do I need a pre-send review process for high-impact engineering announcements?▼

You need a lightweight pre-send review for high-impact engineering announcements. When stakes are high, reviewing the message before sending reduces the risk of public misunderstandings or repeated clarifications across the team.