Product & planning21 categories
One-line release note
A change that needs describing to users, not engineers.
Write this as one release note line a user would understand. No internal names they have never seen.
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Launch and comms. Getting a release out and told: launch plans, go / no-go, release notes, deprecations, post-launch retros.
Related prompts
Build a launch planTwo weeks before a release, to find what nobody has picked up yet.Run a go / no-go checklistThe day before launch, when everyone assumes someone else checked.Announce that a feature is going awayRemoving something people use, and the announcement has to do the hard part.Write release notes people will actually readShipping a version and the changelog currently says "various improvements".Run a post-launch retrospectiveA week after shipping, while the details are still recoverable.Release notes from a changelogA pile of merged changes that needs to become an announcement.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free