release-announcement-writerlisted

# Release Announcement Writer ## Overview Use this skill to turn a shipped change into clear public release communication. The output should be accurate, concrete, and safe to publish: what changed, why it matters, who it helps, where to try it, and what to do next. ## Workflow 1. Gather source material: changelog, release tag, README diff, commit list, issue list, screenshots, demo links, website URLs, and target audience. 2. Separate facts from interpretation. Facts include version, date, links, changed files, features, fixes, and install steps. Interpretation includes value proposition, positioning, and social copy. 3. Identify the release tier: - `patch`: fixes, docs, copy, small polish. - `minor`: new skill, new workflow, new install path, meaningful usability improvement. - `major`: compatibility change, large repositioning, or breaking behavior. 4. Draft the core release summary in plain language before writing channel-specific variants. 5. Write only claims supported by the source material. Avoid inflated wording such as "revolutionary", "first", "complete", or "production-grade" unless the source proves it. 6. Add links to the most useful destination: release tag, GitHub repo, website case study, docs, or demo asset. 7. Finish with a short verification checklist: links work, version is correct, screenshots/GIFs are public-safe, and private implementation details are absent. ## Output Set Create only the formats the user needs. If they ask for a full la