Exec Comms

menkesu/exec-comms

Drafts executive memos and stakeholder communications using Amazon's 6-pager structure, Stripe's memo format, and SCQA framework. Use when writing board updates, executive summaries, or strategic documents.

592 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

385

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/menkesu/awesome-pm-skills --skill exec-comms

The instruction itself

10 sections, as written by the author

Executive Communication

When This Skill Activates

Claude uses this skill when:

Writing executive memos
Creating board updates
Drafting stakeholder emails
Structuring strategic docs

Core Frameworks

Format:

# [Title]

## Executive Summary (BLUF - Bottom Line Up Front)
[Key decision/recommendation in 2-3 sentences]

## Context
[Background needed to understand]

## Analysis
[Data, options considered, tradeoffs]

## Recommendation
[What you propose and why]

## Next Steps
[Specific actions, owners, timeline]

## Appendix
[Supporting data, details]

2. SCQA Framework

Structure:

Situation: Current state
Complication: Problem/challenge
Question: What should we do?
Answer: Your recommendation

Action Templates

Template: Executive Memo

# [Title]: [One-line summary]

## Executive Summary
[Bottom line up front - decision needed or announcement]

## Situation
[Current state, context]

## Complication
[Problem or opportunity]

## Question
[What needs to be decided or understood]

## Recommendation
[Your proposal]

## Rationale
[Why this is the right approach]
- Reason 1
- Reason 2
- Reason 3

## Alternatives Considered
| Option | Pros | Cons | Decision |
|--------|------|------|----------|
| A      | ...  | ...  | Not chosen |
| B      | ...  | ...  | **Recommended** |

## Next Steps
1. [Action] - [Owner] - [Date]
2. [Action] - [Owner] - [Date]

## Success Metrics
- [How we'll measure success]

## Risks & Mitigation
- **Risk:** [describe] → **Mitigation:** [how we'll handle]

Quick Reference

📝 Executive Comms Checklist

Structure:

[ ] BLUF (bottom line first)
[ ] Context clear
[ ] Decision/recommendation obvious
[ ] Next steps specific

Style:

[ ] Concise (no fluff)
[ ] Scannable (bullets, headers)
[ ] Data-backed
[ ] Action-oriented

Key Quotes

Amazon:

> "Start with the press release. Work backwards."

On Executive Writing:

> "If you can't summarize it in 2 sentences, you don't understand it well enough."

How to use it

Copy the folder

Take menkesu/exec-comms from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.