Prompt · Release, Docs
Write release notes users can read
Turn what shipped into user-facing notes and an updated changelog that does not read like a git log.
/release Write user-facing release notes for everything since the last tag and update the changelog.$release Write user-facing release notes for everything since the last tag and update the changelog.@planr-release Write user-facing release notes for everything since the last tag and update the changelog.If /release runs another command, use /planr:release.
With the OpenPlanr plugin for Codex, use $planr:release.
Cursor applies the planr-release rule when you mention it in chat.
Why this works
Release classifies each change by one question: does a user have to do, know, or expect something different now? The notes lead with what users can do, describe fixes by the symptom users saw, and leave internal work out.
Related prompts
Choose the next version number
Decide major, minor, or patch from what changed for users, not from the size of the diff.
Draw the request flow as a diagram
Get SVG, PNG, and an accessible HTML version from one canonical document.
Prepare the merge and deploy steps
Get the ordered landing commands, their preconditions, and the recovery step for the first failure.