Skip to main content
Reference — generated from the toolkit

Source of truth: toolkit/prompts/gtm/release-notes.md. Edit it there; this page is regenerated on build.

Release notes from merged changes

Purpose: generate audience-split release notes from the merged changes in a release — the toolkit ethos applied to the non-engineering half of the business.

Prompt​

From the attached list of merged changes (Conventional Commit messages + PR titles), write release notes in three versions:

  1. Client — what's new and what it means for them, plain language, no internal jargon or ticket IDs.
  2. Support — what changed operationally, what to watch for, any new runbook/KB entries.
  3. Internal — the technical detail. Group by theme, lead with the most valuable change. Do not invent changes not in the list. Flag anything that looks like a breaking change for human review.

Usage notes​

  • Output is reviewed and approved by Commercial/Support at the GTM-readiness gate / release.
  • Part of the GTM & support prompt set (release notes, KB-from-fix, demo-script-from-PFD, client update, beta-feedback synthesis).

Failure modes​

  • Inventing or over-claiming changes (mitigated: "do not invent" + human approval).
  • Leaking internal detail into client notes (mitigated: explicit audience separation).