Release Notes One Pager

Generates a single-page HTML release notes document with a fixed structure: hero, added features, fixes, breaking changes, known issues, upgrade instructions, and a closing CTA. Works from a shared template so you're not writing CSS each time. The workflow is strict about honesty: if you don't provide details for a section, it writes explicit "None" or "No details provided" instead of making things up. Useful when you need a consistent, linkable release announcement page that looks finished even when some sections are empty. All CTAs require real URLs or get removed entirely, no placeholders.

skills.sh installs: 2.9K
GitHub stars: 106.9K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add nexu-io/open-design --skill release-notes-one-pager --agent claude-code

Installs into .claude/skills of the current project.

Files

Release Notes One-Pager Skill

Produce a single-page release notes document in HTML.

Resource map

release-notes-one-pager/
├── SKILL.md                    ← this file
├── example.html                ← quality bar and style reference
├── assets/
│   └── template.html           ← local seed file to copy to project index.html
└── references/
    ├── checklist.md            ← P0 / P1 / P2 gates
    └── layouts.md              ← local section skeletons

Do not write CSS from scratch unless the user explicitly asks for a bespoke structure.

Workflow

Step 0 — Pre-flight

Read assets/template.html.
Read references/layouts.md.
Read active DESIGN.md and map it to the six :root variables.

Step 1 — Start from the shared seed

Copy assets/template.html to project index.html.

Update:

<title>
topnav logo text
topnav link labels (destinations are pre-wired to #added, #fixed, #upgrade-note)
topnav CTA label and href destination, or omit the topnav CTA entirely if no real destination exists
ensure the topnav link targets exist by adding matching section id attributes