Stakeholder Update Skill

This skill creates effective status updates for executives and stakeholders following the BLUF (Bottom Line Up Front) principle.

Required Inputs

Work from what is given. If any of these is missing, still produce the complete output: fill each gap with a reasonable assumption marked (assumed, confirm) and list those assumptions at the end. Ask a question first only when the core subject itself is missing (there is nothing to write about).

• Project or product being reported on
• Audience (CEO, board, cross-functional leads, investors — changes depth and format)
• Period (this week / this sprint / this month)
• Current status (on track / at risk / blocked)
• Key metrics and their current values vs. targets

Reads from / Writes to the Brain

If a professional-brain (brain/) exists, use it before asking:

• Read first: the relevant stakeholders/ files (what each person cares about and their prior asks), context.md (voice/tone), and recent decisions/ for what's changed since the last update.
• Write after: append any new ask, concern, or commitment surfaced to the relevant stakeholders/ file, provenance-tagged ([verbal] for something said in a meeting, not yet documented).