Creates product changelog formats with version notes, categorization (new, improved, fixed), and user-friendly language. Use when documenting product updates for users.
Use this skill when you need to:
DO NOT use this skill for internal release notes (engineering-facing), feature announcements (marketing-facing), or technical API documentation. This is for user-facing product changelogs.
A CHANGELOG BUILDS USER TRUST BY SHOWING CONTINUOUS IMPROVEMENT — WRITE EVERY ENTRY SO A NON-TECHNICAL USER UNDERSTANDS WHAT CHANGED AND WHY IT MATTERS TO THEM.
| Input | What to Ask | Default |
|---|
| Product name | "What product is this changelog for?" | No default — must be provided |
| Update frequency | "How often do you ship updates? Weekly, biweekly, monthly?" | Biweekly |
| Audience | "Are changelog readers technical or non-technical?" | Non-technical business users |
| Current changes | "List the changes in this update — features, improvements, and fixes." | No default — must be provided |
| Version numbering | "Do you use version numbers, dates, or both?" | Date-based (e.g., January 15, 2026) |
| Distribution | "Where does the changelog live? In-app, blog, email, dedicated page?" | Dedicated changelog page |
GATE: Confirm the brief before writing.
Every change falls into one of these categories:
Each changelog entry follows this structure:
### [Date or Version]
**New**
- **[Feature name]** — [What it does and why it matters in one sentence]
**Improved**
- **[Feature name]** — [What changed and the user benefit]
**Fixed**
- **[Issue description]** — [What was broken and confirmation it is resolved]
GATE: Confirm the category system and format before writing entries.
| Category | Length | Detail Level |
|---|---|---|
| Major new feature | 2-3 sentences | Benefit + how to access it |
| Minor improvement | 1 sentence | What changed + benefit |
| Bug fix | 1 sentence | What was broken + resolved |
| Deprecation | 2-3 sentences | What, when, migration path |
Provide a recommended page layout:
## Changelog Quality Checklist
- [ ] Every entry starts with a benefit, not a technical description
- [ ] Changes are categorized as New, Improved, or Fixed
- [ ] Each entry is one sentence (major features may use 2-3)
- [ ] Active voice used throughout
- [ ] Bug fixes describe what was broken specifically
- [ ] No jargon — readable by non-technical users
- [ ] Date or version number is included
- [ ] Deprecated features include migration guidance
- [ ] Subscribe/notification option exists for the changelog page
### February 15, 2026
**New**
- **Recurring invoices** — Set any invoice to automatically send on a schedule (weekly, monthly, or custom). Find it under Invoice Settings.
- **Client portal** — Your clients can now view all their invoices and payment history in one place. Share the link from any client profile.
**Improved**
- **Dashboard loading speed** — Dashboard now loads 60% faster, especially for accounts with 500+ invoices.
- **CSV exports** — Exports now include payment status and date columns by default.
**Fixed**
- **Tax calculation on discounted items** — Tax was calculated before the discount was applied, resulting in overcharges. Now calculates correctly on the discounted amount.
- **Email notifications** — Some users were not receiving payment confirmation emails. Resolved for all accounts.