What problem does it solve? Writing stakeholder updates means manually digging through merged PRs, closed issues, commit history, and architecture decisions, then reshaping that raw activity into an audience-appropriate narrative. This Skill automates the gathering and synthesis so updates are consistent, evidence-linked, and tailored to their audience. ## Core Features & Use Cases - Audience-aware formats: weekly updates are dense and tactical for the team, monthly updates are strategic and metrics-driven for leadership, and launch updates are celebratory and outcome-focused for broader audiences. - Evidence-grounded synthesis: pulls merged PRs, closed issues, commit history, open PRs, and ADRs via the GitHub CLI and git, linking every claim to real PR or issue numbers. - Template-driven output: fills the shipped stakeholder-update template and writes the result to omnigrid/artifacts/updates/<type>-<YYYY-MM-DD>.md. - Use Case: At the end of a sprint, run the weekly mode to produce a 300-500 word update covering what shipped, what is blocked, and what is next, with links to every referenced PR and issue. ## Quick Start Ask the assistant to generate a weekly stakeholder update covering the last seven days of merged PRs, closed issues, and ADRs, and save it to the updates artifacts folder.
