What problem does it solve? Teams struggle to write public project communication that speaks as the project itself — release notes, announcements, and status updates often bury breaking changes, oversell features, or confuse mixed audiences of experts and newcomers. ## Core Features & Use Cases - Announcement structure: Enforces a fixed shape — what changed, who is affected, action required, compatibility/rollout, and links — so readers get the key facts in the first lines. - Changelog-first workflow: Maintains a Keep a Changelog file with SemVer discipline, then derives the human-readable release note as a curation of it, flagging version-number mismatches honestly. - Register-specific guidance: Covers warm-but-concrete feature announcements, factual incident status updates, and tightened security advisories with affected versions, impact, and mitigation. - Use Case: After shipping a release with a breaking change, use this Skill to update the changelog, then draft a release note that names the break up front and details migration steps under compatibility. ## Quick Start Use the writing-community skill together with writing-core to draft a release announcement for version 2.1.0 based on the current changelog.
