Communicate
Input: $ARGUMENTS
Step 1: Define the Communication
MESSAGE ESSENCE: [In one sentence, what needs to be communicated]
SENDER: [Who is communicating]
CONTEXT: [Why this communication is happening now]Step 2: Know the Audience
AUDIENCE: [Who will receive this]
AUDIENCE SIZE: [One person / small group / large group / public]
AUDIENCE STATE:
- They currently know: [what they already understand]
- They currently feel: [their likely emotional state]
- They currently expect: [what they think is coming]
AUDIENCE NEEDS:
- They need to know: [essential information]
- They need to feel: [desired emotional outcome]
- They need to do: [desired action, if any]Step 3: Set the Goal
What type of communication is this?
| Goal | Signal |
|---|---|
| Inform | Audience needs to know something |
| Persuade | Audience needs to change their mind or agree |
| Instruct | Audience needs to do something specific |
| Align | Multiple parties need to reach shared understanding |
| Inspire | Audience needs motivation or energy |
PRIMARY GOAL: [Inform / Persuade / Instruct / Align / Inspire]
SUCCESS LOOKS LIKE: [What the audience thinks, feels, or does after]Step 4: Choose Medium and Structure
RECOMMENDED MEDIUM: [Email / meeting / document / presentation / conversation / message]
REASON: [Why this medium fits the audience and goal]
STRUCTURE:
1. [Open with: hook, context, or headline]
2. [Core content: the main message]
3. [Support: evidence, examples, or detail]
4. [Close: action item, next step, or summary]Step 5: Anticipate Reactions
LIKELY QUESTIONS:
- [Question 1] — answer: [brief response]
- [Question 2] — answer: [brief response]
LIKELY OBJECTIONS:
- [Objection 1] — response: [how to address it]
- [Objection 2] — response: [how to address it]
EMOTIONAL REACTIONS:
- [Possible reaction] — handle by: [approach]Step 6: Draft the Communication
Write the actual message, applying all of the above.
[DRAFT]
[The complete communication, ready to use or refine]
[/DRAFT]TONE CHECK: [Does the tone match the audience and goal? Adjust if needed]
LENGTH CHECK: [Is it the right length? Shorter is almost always better]
CLARITY CHECK: [Could anyone misunderstand this? Fix ambiguity]
GENERATION FAILURE CHECK:
- Voice collapse: Could any AI assistant have written this? If the communication sounds interchangeable with a template, rewrite with the sender's actual voice — word choices, rhythms, specificity that only THIS person in THIS context would use.
- Cached takes: Is any part of the message something that's been said in 10,000 other communications? ("We're excited to announce..." / "In today's fast-paced environment..." / "We value your partnership.") Replace with something only true of THIS situation.
- Performed humility: Is there a "to be sure" or "we recognize" paragraph that exists to look balanced? Delete it. If the piece is the same or better without it, it was performance.Integration
Use with:
/tmsk-> Understand team dynamics before communicating/orgn-> Understand organizational context/indv-> Tailor communication to a specific person/stl-> Refine the writing style