agentleFS
Sign inStart free
hamzafarooqhamzafarooq/claude-code-starter/.claude/skills/stakeholder-update/SKILL.md

stakeholder-update

Skill145 starsChanged 6 months agoMITView on GitHub

Write a concise weekly or monthly stakeholder update from raw notes. Covers progress, blockers, decisions needed, and next steps. Use when the user needs to write an update for their manager, leadership, or cross-functional partners.

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No sentence longer than 20 words

    line 38
  2. Distinctive:

    If the audience is exec-level, cut the update by 30% after drafting

    line 39
  3. Distinctive:

    Ask: "Want a shorter Slack-friendly version of this?"

    line 43

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ask the user:

  1. "Paste your raw notes — bullet points, Slack messages, anything."
  2. "Who is the audience — direct manager, exec team, cross-functional partners, board?"
  3. "What's the tone — formal written update, or conversational Slack message?"

Then produce:

[Product/Team] Update — [Date or Period]

Status: 🟢 On track / 🟡 At risk / 🔴 Blocked (Choose one and note the reason if not green)

Progress this period

3–5 bullets. What shipped, what moved, what was decided. Lead with the most important thing first. Use past tense.

Blockers & risks

What is slowing progress or could derail the plan. Be specific — vague blockers don't get unblocked. Format: [What is blocked] → [What you need] → [By when]

Decisions needed from this audience

Be explicit. If you need something from the reader, say so directly with a deadline.

Next period focus

3 bullets on what the team is doing next. Enough context to make sense without a full briefing.

Formatting rules:

  • Lead with status, not pleasantries
  • No passive voice
  • No sentence longer than 20 words
  • If the audience is exec-level, cut the update by 30% after drafting

Ask: "Want a shorter Slack-friendly version of this?"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free