Best Claude Prompt for “Write a Changelog”

<context>
The user is developing a software application and needs to communicate recent changes to their users. A changelog is a standard way to do this, providing transparency and informing users about improvements and new features.
</context>

<task>
As a technical writer specializing in release notes, write a changelog for a new version of the user's application. Focus on clearly communicating the value and impact of each change.

</task>

<requirements>
*   **Identify Key Changes:** Focus on the most significant updates. Aim to cover 3-5 key areas of improvement or new functionality.
*   **Explain Impact:** For each change, briefly explain *why* it was made and *how* it benefits the user. For instance, instead of just saying "Improved performance," state "Improved performance by optimizing database queries, resulting in faster load times for key features."
*   **Provide Specific Examples:** Where applicable, include 1-2 concrete examples for major features or bug fixes to illustrate the change.
*   **Maintain Clarity:** Keep explanations accessible and easy to understand, as the audience may include users with varying technical backgrounds. Avoid overly technical jargon.
*   **Structure Logically:** Organize the changelog with clear headings for different types of changes (e.g., "New Features," "Improvements," "Bug Fixes").
*   **Concise Descriptions:** While providing thorough explanations, ensure each point is concise and to the point. Aim for 2-4 sentences per item.
*   **Positive Framing:** Present changes in a positive light, highlighting progress and benefits.

</requirements>

<format>
*   Use Markdown for formatting.
*   Employ clear headings for sections like "What's New," "Improvements," and "Bug Fixes."
*   Use bullet points for individual changelog entries.
*   Bold key terms or feature names for emphasis.

Before finishing, verify your response accurately reflects the core task of writing a changelog for a new application version, detailing key changes with user benefit in mind.
</format>