release-announcement

Write channel-appropriate release announcements including changelogs, blog posts, and social posts.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill release-announcement-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-announcement
Source: https://github.com/adamtpang/summon.company/tree/main/packages/skills-catalog/catalog/optional/content/release-announcement
Command: npx skills add https://github.com/adamtpang/summon.company --skill release-announcement-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping a release requires different writeups for different surfaces, and teams often produce vague, filler-heavy announcements that bury migration steps and fail to tell readers whether the release affects them. ## Core Features & Use Cases - Channel-Specific Templates: Provides distinct structures for changelog entries, release notes, dev blog posts, in-app notes, and social posts. - Audience-First Framing: Maps audiences (power users, API adopters, prospects, internal teams) to the right channel, tone, and content shape. - Paperclip Cases Integration: Optionally persists release, blog post, and tweet storm cases via the Paperclip Cases API when running inside Paperclip. - Use Case: A team shipping v1.42.0 with a breaking change uses this Skill to produce a terse changelog entry, a migration-focused release note, and a one-sentence social post, each tailored to its surface. ## Quick Start Write a changelog entry and a short social post for version 2.1.0 of my app, which adds CSV export and deprecates the legacy XML API.

Frequently Asked Questions about release-announcement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a release announcement for a new version?

Lead with what changed in one sentence, name who it affects, and state what the reader must do. Then pick the channel template: terse changelog for existing users, release notes with migration guides for adopters, or a 300-800 word blog post for broader audiences.

What is the difference between a changelog entry and release notes?

A changelog entry is a terse, categorized list (Added, Changed, Fixed, Deprecated, Breaking) with one-line user benefits. Release notes add migration guides with before/after code, compatibility tables, known issues, and contributor acknowledgements.

How should breaking changes be communicated in release announcements?

Mark breaking changes with a "**Breaking:**" prefix in the changelog, include an explicit migration path or link, and repeat the warning in email and social channels. Broadcast breaking changes before users encounter them, and ensure the upgrade guide contains the same information.

When should I not write a release announcement?

Skip announcements for internal-only changes with no user impact; update internal docs instead. Also wait if the release is still in active development, since pre-announcing unshipped work creates broken promises.

Does this skill work with the Paperclip Cases API?

Yes, when running inside Paperclip with experimental.enableCases enabled, it upserts release, blog post, and tweet storm cases and writes copy via PUT /api/cases/:caseId/documents/body. If the API returns 403 Cases are disabled, it reports the limitation and continues with the copy artifact.