Consulting Stakeholder Update

Workspace: use the selected project and its AGENTS.md; keep existing entity folders and Reality headings. Business paths below are relative to that project. Bundled resources are relative to this installed skill; sibling capabilities resolve by their installed names. Never search another private checkout for missing inputs. Use workspace identity, audience, pricing, and DESIGN.md fonts.

The style for a short note to a stakeholder: a recap after a working session, a milestone update, or a "here's what surfaced and what I need" flag. It sits on top of recoup-internal-consulting-outbound-email (the process: read all context first, route the ask to the right person, gate before sending) and recoup-internal-consulting-copy-writer (the voice: no em-dashes, short and direct, cool/calm/confident). This skill adds the shape and the feel for updates specifically.

Not rigid. This is a set of principles and a shape to riff on, not a template to fill. Adapt to the person and the moment. Drop any section that earns nothing. The goal is a note that reads like a trusted partner wrote it in two minutes, not a status report.

Three principles

Simplicity — fewer words, faster read.

• Lead with the headline in line one. No throat-clearing ("I wanted to reach out").
• One idea per sentence. If a word earns nothing, cut it.
• Group anything list-like into tight bullets (reasons, tools, next steps). Bullets scan faster than prose.
• One clear ask with a low-effort default ("connect me with X and I'll take it from there"), not a menu.
• Shorter than feels natural. A recap rarely needs more than ~150 words.

Clarity — the reader knows exactly what happened, what you need, and from whom.

• Plain words a non-expert would say out loud. No jargon, no insider verbs.
• Make the win explicit, so a setup-heavy session never reads as a bust.
• Frame a blocker as a finding plus the fix, never a complaint.
• Route each ask to the right owner (IT vs ops vs the sponsor); name names when you can.
• Every fact, name, and product name correct (e.g. Wispr Flow, not Whisper; Git is the machine, GitHub is hosting).

Play — keep the human in it.

• Match the relationship's tone. With a warm contact a casual sign-off ("Ok byyyyyeeeee") beats a stiff one; with a formal one, dial it back.
• Confident and easy, never needy. No "just checking in," no apologizing for their time.
• A little personality and warmth is the point. This is a note from a partner who's enjoying the work, not a corporate update.

The shape (use what serves; reorder freely)

1. Headline — one warm line: what happened / how it went.
2. What we did — a sentence or two of real progress (the win).
3. What surfaced + the ask — the blocker or finding, framed as solvable, with the ask routed to the right person. Bullets if it's a list.
4. Quick notes — tools, recommendations, side items. Bulleted, brief.
5. Next — the forward look (next session booked, momentum).
6. Sign-off — with personality that fits the relationship.

Gut check before sending (read it as them, don't grind a checklist)

• Could a busy person get the point and the ask in one skim?
• Is the win obvious and the blocker framed as solvable?
• Is the ask aimed at the right person and low-effort for them?
• Does it sound like you, not a status bot? (And zero em-dashes — see recoup-internal-consulting-copy-writer.)

Worked example — fictional session recap

All names, companies, and events in this example are invented.

Hey Morgan,

Jordan and I tested the new intake flow at Cedar Lantern Studio today. The team can now turn a request into a draft brief without copying it across three documents.

One thing needs fixing before the pilot: the shared folder is read-only for the coordinators. Could you connect us with whoever manages folder access? I'll send them the exact change we need.

Once access is sorted, Jordan will try it with the next request and tell us what breaks.

Thanks, Alex

Why it works: the result comes first, the blocker has a concrete fix, and the sponsor has one clear ask. Replace every example fact with evidence from the actual engagement.