changelog-voice
Changelog Voice
Ship updates people actually want to read.
How to use
/changelog-voiceApply changelog constraints to this conversation.
Constraints
Entry Structure
- What changed (specific, concrete, no marketing language)
- Why it matters (what the user can now do that they couldn't before)
- How to use it (link or brief instruction)
Rules
- MUST lead with the user benefit, not the technical change
- MUST categorize: New, Improved, Fixed, Removed
- SHOULD include a visual (screenshot, gif, video) for UI changes
- NEVER say "various bug fixes" without specifics
- NEVER announce something as "new" that was previously broken and is now working
- SHOULD mention breaking changes prominently with migration steps
Tone
- Direct, not corporate ("You can now..." not "We are pleased to announce...")
- Honest about what's still missing or in progress
- Brief. Respect the reader's time.
- SHOULD acknowledge when a change was user-requested ("You asked, we built it")
Anti-Patterns
- Changelogs that read like marketing emails
- Burying breaking changes in a long list of improvements
- Announcing features that aren't actually available yet
- Using changelogs as a growth channel (no "invite a friend" CTAs in release notes)
- Updates without dates
More from dragoon0x/product-skills
prd-writing
Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.
1freemium-vs-paid-gate
Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.
1error-recovery
When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.
1cta-patterns
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
1onboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
1user-psychology
Apply motivation, friction, and trust patterns to product decisions. Maps cognitive biases and behavioral triggers to specific UI and copy choices. Use when reviewing flows for drop-off points or when something feels right but doesn't convert.
1