skills.rest
GeneralJerel
GeneralJerelCOMMUNITY
Explore all skills by this author →
GitHub

create-stakeholder-update

Generate structured stakeholder updates with BLUF, statuses, risks, and metrics.

6|Updated Feb 19, 2026
Search Tags:#automation#documentation#metrics#status#stakeholder#update#bluf
One-click install
npx skills add https://github.com/GeneralJerel/chalk-skills --skill create-stakeholder-update
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-stakeholder-update
Source: https://github.com/GeneralJerel/chalk-skills/tree/main/skills/create-stakeholder-update
Command: npx skills add https://github.com/GeneralJerel/chalk-skills --skill create-stakeholder-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of structured stakeholder updates from project context, reducing manual drafting time and ensuring consistency across communications.

Core Features & Use Cases

  • Generate BLUF-based summaries from project context (docs, git activity, PRs) to inform leadership.
  • Produce per-workstream statuses with traffic-light indicators and concise explanations.
  • Categorize risks into FYI and Needs Decision, surfacing required actions.
  • Include a metrics snapshot when a framework exists; otherwise note that metrics tracking is not yet established.
  • Determine the next file number by inspecting existing product docs and save the output as a numbered Markdown file in .chalk/docs/product.

Quick Start

Generate the latest stakeholder update for the current period using the available project context and save it as the next numbered file under .chalk/docs/product.

Frequently Asked Questions about create-stakeholder-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate stakeholder updates with BLUF from project context?▼

Automating stakeholder updates involves generating BLUF narratives, per-workstream traffic-light statuses, categorized risks, and metrics snapshots from project docs and activity, saving the output as a numbered Markdown file.

What is the best way to generate executive status reports for multiple workstreams?▼

Generating executive status reports for multiple workstreams requires structuring project context into BLUF summaries, applying traffic-light indicators per workstream, and categorizing risks into FYI and Needs Decision to surface required leadership actions.

How do I include a metrics snapshot in my periodic project update?▼

Including a metrics snapshot in periodic project updates automatically populates the report if a tracking framework exists; otherwise, it explicitly notes that metrics tracking is not yet established within the generated document.

Where are automated stakeholder update files saved in the project directory?▼

Automated stakeholder update files are saved as numbered Markdown files in the .chalk/docs/product directory, determining the next file number by inspecting existing product documentation to maintain sequential ordering.

How are project risks categorized for leadership reporting?▼

Project risks for leadership reporting are categorized into FYI and Needs Decision buckets, directly surfacing required actions and decisions from the project context to ensure executives know when intervention is necessary.

Related Skills

Explore More Content & Communication Skills→
jerelvelardejerelvelarde
6

create-stakeholder-update

Generates decision-oriented stakeholder update reports in Markdown from docs and git activity.

Community
Intermediate
giadaf-booshagiadaf-boosha
10

stakeholder-comms

Create tailored stakeholder communications with templates for executives, engineers, partners, and customers.

Community
Intermediate
ojiudezueojiudezue
1

vibememo-eval

Capture project decisions and evaluate documentation quality across 9 dimensions.

Community
Intermediate
Leeky1017Leeky1017
1

Shrink

Condense long text blocks while preserving key facts and narrative voice.

Community
Basic