What problem does it solve? Keeping a README's "What's new" section consistent after each release is easy to get wrong: entries become verbose, internal refactors get listed, and formatting drifts. This Skill enforces a compact, braggable-features-only format for release highlights that also render on nuget.org via the packed readme. ## Core Features & Use Cases - Entry filtering rules: Only user-facing features worth bragging about qualify; internal refactors, bug fixes, and dependency bumps are excluded. - Strict entry shape: Each entry is a bold title plus a doc or ADR reference link, with the version number included only when the entry shipped under it. - Ordering and linking conventions: Newest entries go at the top, ADRs are linked when they exist, and patch releases without braggable features get no entry. - Use Case: After shipping release 1.42.0 of a .NET tool, add a single bold-titled bullet linking to the relevant ADR instead of writing a prose changelog paragraph. ## Quick Start Update the README What's new section for the latest release following the compact entry rules.