← ClaudeAtlas

release-notes-writerlisted

Generate slide content for the Product section of a leadership weekly / release-notes deck. Aggregates user-visible product ships from the last 4 weeks across all of the business's repos (the current git repo + every repo in business.json → stack.code_repos[]) plus Jira Done items in ${PROJECT_KEY}, groups them by theme, and produces per-experiment slides with measured impact tables. Use when asked for 'leadership product slides', 'product week deck', 'release notes deck', 'what shipped to production', '/leadership-product-weekly', or '/product-weekly'.
mohitkhandelwal242/ai-pm-operator · ★ 0 · AI & Automation · score 62
Install: claude install-skill mohitkhandelwal242/ai-pm-operator
# Leadership Product Weekly — Slide Content Generator Generate slide-by-slide markdown for the **Product** section of the business's leadership weekly / release-notes deck. The output is paste-ready for Google Slides. **Audience:** leadership (CEO / founders / exec team). They want to know *what user-visible product shipped* and *what measurable impact each had* — not a git log, not infra/tooling work. The skill is generic: it builds the Product section from whatever repos and Jira project the business has configured. There is no hard-coded deck or repo list — everything comes from `business.json` and `.env`. --- ## Step 0 — Load business context & resolve window Read `business.json` first: - `stack.code_repos[]` — the set of repos to scan (in addition to the current git repo). - `metrics.key_metrics[]` — the metrics to lead impact tables with. - `company.revenue_model` / `company.product_name` — framing for the slide narrative. Resolve the window: - Default: **last 4 weeks ending today**. - Override: `/leadership-product-weekly 2026-04-19 2026-05-19` (start, end). Bind: - `START_DATE` → start of window (default: today − 28 days, midnight local) - `END_DATE` → end of window (default: today, 23:59 local) - `MONTH_TAG` → e.g. "May '26, Week 3" derived from `END_DATE`'s month + ISO week-of-month --- ## Step 1 — Resolve repos Build the repo set from `business.json` → `stack.code_repos[]`, plus the current git repository: ```bash source .env 2>/dev/null # Current repo