release-notes-one-pager

release-notes-one-pager is a skill for producing a single-page release notes document in HTML. It solves the problem of turning version changes into a clean, consistent one-pager covering highlights, Added, Fixed, Breaking changes, Known issues, and an Upgrade note. A distinctive design goal is honesty: when the user does not supply details, the skill writes explicit "None" style placeholders (for example "No fixes provided" or "None reported") and uses an em dash for missing version or date fields rather than inventing content.

The skill ships a full local resource bundle: an example.html quality reference, an assets/template.html seed to copy into the project's index.html, and references files (layouts.md with eight paste-ready section skeletons and checklist.md with P0/P1/P2 gates). Its workflow is explicit: a pre-flight step reads the template, layouts, and the active DESIGN.md mapped to six :root variables; it starts from the shared seed and updates the title, nav, and CTAs; it composes a fixed section order (hero, added, fixed, breaking changes, known issues, upgrade note, closing CTA) with required section id attributes; it enforces honest placeholders for missing details; it runs the checklist so every P0 passes; and it emits the result wrapped as an HTML artifact. A strong safety-conscious rule requires every CTA to use a real, safe destination or be omitted entirely, explicitly forbidding placeholder hrefs or misleading anchors.

The target users are engineering and product teams, release managers, and technical writers who need to publish professional, consistent release notes or changelogs quickly, especially within a design-system-driven HTML prototyping workflow.