Tech Founder Notes

    Create a clear, useful, and engaging changelog

    A good changelog doesn't just list changes: it informs, values, and reassures. Whether for your users or your teams, it must be structured, concise, and adapted to the target audience. This prompt helps you write a readable and professional changelog from your technical backlog.

    When to use this prompt

    At each production deployment or product release

    To publish your release notes on a public changelog

    To inform your B2B clients of important evolutions

    To summarize changes internally (sales, support…)

    What this prompt helps you achieve

    A changelog structured by type of change

    A version understandable even by non-tech users

    A tone consistent with your brand image

    A reusable communication support (email, helpdesk…)

    Tips and mistakes to avoid

    ✓Do's

    • •Avoid unexplained technical terms
    • •Don't overload with too many secondary details
    • •Highlight benefits for the end user
    • •Keep a repeatable structure for each new version

    ✗Don'ts

    • •Avoid overly long lists without hierarchy
    • •Don't neglect context and user benefits

    Prompt Template

    This is the base template with placeholders. Replace the placeholders with your specific information:

    You are a Product Manager in charge of product communications. Write a clear and structured changelog from the following changes: {{change_list}}. The target audience is: {{target_audience}}. The desired tone is: {{tone}}. Organize the information into categories if necessary (new features, improvements, fixes) and ensure it remains understandable and concise. {{additional_context_block}}

    Placeholder descriptions:

    {{change_list}}List of changes - e.g., Slack integration added, dashboard loading speed improved, CSV export bug fixed…
    {{target_audience}}Target audience - e.g., end users, beta testers, B2B clients, internal team
    {{tone}}Desired tone
    {{additional_context}}Additional information (optional) - e.g., add a link to documentation or specify affected versions

    Example of generated prompt

    Here's an example with filled-in values:

    You are a Product Manager in charge of product communications. Write a clear and structured changelog from the following changes: Slack integration added, dashboard loading speed improved, CSV export bug fixed. The target audience is: end users. The desired tone is: warm and enthusiastic. Organize the information into categories if necessary (new features, improvements, fixes) and ensure it remains understandable and concise. Also add these details: add a link to documentation and indicate affected versions.

    Share this prompt

    Help others discover this useful prompt by sharing it on social media