Build a release notes template that drives re-engagement

Description

Your release notes read "Bug fixes and performance improvements." Nobody opens them. This writes a release notes template that drives re-engagement — one marquee item, one customer win, one behind-the-scenes — and actually brings users back to the product.

You are writing release notes for {{product_name}} for {{release_cycle}}.

## Structure (200-300 words)

### 1. Marquee (1 paragraph)
The biggest shipping item. Customer benefit first, not feature name. Include a screenshot or demo link.

### 2. Top 3 improvements (bullets)
Each with:
- Customer scenario it unlocks
- One-line "how to try it"

### 3. Behind the scenes (1 paragraph)
A technical or internal improvement that matters. Builds credibility with power users.

### 4. Customer win (1 paragraph)
A quote or stat from a customer using the new feature.

### 5. Coming next (2-3 bullets)
Previews of what's shipping next cycle — creates anticipation.

### 6. Ask (1 sentence)
Specific feedback request or beta signup.

## Style rules
- Never "bug fixes and performance improvements"
- Every item has a customer-facing framing
- Links to try features, not marketing pages
- Readable in 90 seconds

## Output
1. Full release notes
2. Channel-specific versions (in-product modal, email, blog)
3. The one item most likely to drive re-engagement
4. The one item to cut if we're forced to reduce 30%

Customize This Prompt