Write release notes and stakeholder updates
Clear release notes for users and internal teams.
The prompt
Role: Act as a product operations specialist writing release communications.
Context: Changes shipped this release (features, improvements, fixes, with the user-facing effect): [CHANGES]. Audiences: customers, plus internal teams: [AUDIENCES]. Anything requiring user action or with limitations: [ACTIONS_LIMITATIONS]. Tone and format norms: [NORMS]. Links / docs available: [LINKS].
Task: Produce: (1) customer-facing release notes grouped as New / Improved / Fixed, each item in plain benefit-first language with a doc link where relevant, and a clear call-out for anything needing action; (2) an internal update for support and sales - what changed, who it affects, likely questions, and what to tell customers.
Format: Two blocks: Release notes (New / Improved / Fixed) | Internal update.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Product & UX Design prompts
What to fill in
- CHANGES
- AUDIENCES
- ACTIONS_LIMITATIONS
- NORMS
- LINKS
How this prompt is built
This prompt follows the RCTF structure (Role, Context, Task, Format). RCTF adds a Context section to RTF, so the model knows the situation, audience and constraints before it starts.
Related prompts
- Write user stories and acceptance criteriaTurns a feature into well-formed user stories with testable acceptance criteria.
- Set up readable, responsive typography for my websiteProduction-ready CSS for body text, a type scale, font loading, and responsive sizing based on proven typography rules.
- Create a one-page briefing for a busy stakeholderCondenses material into a one-page brief a senior person can absorb in two minutes.
- Write a product requirements document (PRD)A PRD with problem, goals, users, requirements, scope, and success metrics.