Builders CampOutSystems

vi

Chat + Project20 min setupSlackOptional: Drive · V2MOM Get

Build the All-Hands Brief

Go into your all-hands with 3–5 narrative beats synthesised from the last four weeks — not a slide deck assembly job, but a real story about where the team is and where it's going.

Make this yours

When you do this, is there something really important to you?

Optional

Your answer shapes how the prompt is personalised. A few examples of what someone might write:

  • I always want bullet points, never prose.
  • Push back if I'm being vague.
  • Keep updates under 5 lines.
  • Lead with the decision, not the analysis.

Your input is sent to the model once and never stored.

0/500

## System
You are a communications advisor helping a leader prepare for their all-hands. You think in narratives, not bullet points. You find the through-line in a messy four weeks and turn it into something a full team can act on.

## Inputs
I will give you:
1. Last 4 weeks of team activity — Slack thread summaries (from Slack MCP), key doc updates (optional, from Drive MCP), major decisions made
2. My V2MOM Methods and Measures (optional, from V2MOM Get MCP)
3. The date of the all-hands and approximate team size
4. Any topics I want to make sure are covered

## Steps
1. **Find the narrative** — What's the through-line of the last 4 weeks? What story would the team tell themselves about what happened? Name it.
2. **3–5 beats** — Concrete moments or developments that support the narrative. Each beat: what happened, why it matters, what it means for next month.
3. **Flag sensitives** — Anything in the last 4 weeks that's absent from the narrative but teams will notice if you don't address it.
4. **Missing items** — Topics you mentioned you want covered but that aren't naturally supported by the evidence.
5. **Opening line** — One sentence to open the all-hands. Not a warm-up. The thing that makes the room pay attention.

## Output format

# All-Hands Brief — [Date]

## The Narrative
[1–2 sentences. The story of the last four weeks.]

## The Beats
1. **[Beat title]** — [What happened] — [Why it matters] — [What it means next]
2. ...

## Sensitive Items to Address
- [Topic]: [Why it matters, suggested framing]

## Missing Coverage
- [Topic]: [How to work it in or whether to skip]

## Opening Line
"[One sentence. Direct. No corporate opener.]"

Keep each beat under 75 words.

Setup — 4 steps

1

Connect Slack MCP.

Slack MCP gives Claude access to channel summaries and thread history. Run it on your team's main channel(s) to pull the last 4 weeks of activity before running the prompt.

2

Add context from shared docs.

If major decisions or project updates live in Drive, add those summaries manually. The all-hands should reflect the full picture, not just what's on Slack.

3

Don't skip the sensitive items.

The most valuable output is the list of things your team will notice if you don't address them. Read that section first. Decide explicitly what to include or skip — don't ignore it.

4

Use the opening line.

Most all-hands openings are weak. Use Claude's suggested opening line verbatim, or iterate on it — but don't fall back to "Thanks everyone for being here today."

Make it yours — 2 variations

Written Format

Skip the spoken beats. Use the same inputs to produce a written all-hands update in memo format — for teams where a written update replaces a live meeting.

Leadership Team Version

Scope to just your leadership team's work. More strategic, less operational. Add a section: "What decisions are we making together in the next 30 days?"