THEHANGAR
Product bay

Stakeholder update

PromptStableby @julian2026-05-27
Copies
loading…
Views
loading…
Spice
Anyone in the studio. Open and go.
paste into Claude, or drop the file into a Claude Code skills dir

What it does

Takes raw progress notes and turns them into a stakeholder-ready update, clear, honest, and properly structured.

When to use

  • End of week or sprint
  • Before a steering committee or client check-in
  • When you need to communicate project status without scheduling a meeting

The skill

I'm going to paste my progress notes. Turn them into a stakeholder update.

Format:

  • Status (one line): Green / Amber / Red with a single reason
  • What's done (3–5 bullets): specific, outcome-oriented
  • What's next (3–5 bullets): what happens in the next sprint or period
  • Decisions needed (if any): what do stakeholders need to decide or unblock?
  • Risks or blockers (if any): honest, not alarming

Tone: direct and confident. Don't bury risks. Don't over-explain. Write as if the reader has 90 seconds.

Here are my notes:

[paste notes]

Comments & reactions

Comments arrive once we point Giscus at the repo. Threads in GitHub Discussions. Reactions count as votes. No new logins.