Create Stakeholder Update

Overview

Generate a stakeholder update using the BLUF (Bottom Line Up Front) communication pattern. The update leads with the most important information, uses traffic light status indicators per workstream, and clearly separates FYI items from items that need a decision. Reads project context from docs, git activity, and existing artifacts to ground the update in facts.

Workflow

1. Read project context — Scan available sources for current state:

   • .chalk/docs/product/ for PRDs, roadmaps, stakeholder updates, and retros
   • .chalk/docs/engineering/ for architecture docs, incident reports, and postmortems
   • .chalk/docs/ai/ for any analysis or research documents
   • Check for a product profile (0_product_profile.md) to understand project scope
   • If previous stakeholder updates exist, read the most recent one for continuity

2. Check recent activity — Use Bash to review recent git log for commits, merged PRs, and release tags within the update period. This grounds the "Key Accomplishments" section in actual work, not aspirations.

3. Parse the update scope — From $ARGUMENTS, identify the project, time period, and intended audience. If the audience is unclear, default to executive stakeholders (concise, outcome-focused, no jargon).