release-reportlisted

# Release Report — Client Release Communication Reads a version entry from `CHANGELOG.md` and produces a plain-English release report for the client. Not a technical document — written as a friendly update in studio voice. --- ## Invoke ``` /release-report /release-report 1.2.0 ``` If no version is provided, reads the most recent entry from `CHANGELOG.md`. --- ## Steps ### 1. Read CHANGELOG.md ```bash cat CHANGELOG.md ``` Find the requested version section (or the first/most recent `## [X.Y.Z]` block if none specified). Extract entries by category: Added, Fixed, Changed, Removed. If `CHANGELOG.md` does not exist or the version is not found, stop and tell Mark to run `/changelog` first. ### 2. Read brand voice Read `$STUDIO_CONTENT_DIR/internal/brand.md` for voice guidance. Apply the **"Client messages (existing relationships)"** register: - Direct, no filler openers - Plain English, no technical terms - Short sentences - Sign off with "Cheers" ### 3. Read project context Read `CLAUDE.md` for: - Client name - Project name - Any notes on communication preferences ### 4. Write the report Map changelog categories to client-friendly headings: | Changelog | Report heading | |---|---| | Added | What's new | | Fixed | Issues resolved | | Changed | Updates | | Removed | Removed | Omit any empty categories. Omit the "Removed" section unless there is something the client needs to know about. Write each item in plain English describing what the client will notice — n