Write Release Notes
The scenario
You're launching a feature and need release notes that users will actually read. Not a list of technical changes — a benefit-first announcement that makes people want to try it. You need versions for your changelog, email, and maybe an in-app banner, and they all need slightly different tones.
Example output
🚀 New: Checkout in 2 Steps (Not 5)
Enterprise teams, you asked — we listened. Buying just got a lot faster.
What Changed
Your checkout now auto-fills billing details from your company profile and lets you add PO numbers after the purchase. What used to take 5 steps now takes 2.
Why It Matters
- Save 3 minutes per purchase — no more hunting for billing codes
- "Complete Later" for PO numbers — don't block a purchase because finance hasn't assigned a PO yet
- Saved payment methods — set up once, buy instantly going forward
How to Use It
- Go to checkout as usual
- Your billing info auto-fills from your company profile
- Click "Complete Purchase" (or "Add PO Later" if you need to)
That's it. No setup needed.
Details
- Available to all Enterprise plans starting today
- Saved payment methods: Settings → Billing → Payment Methods
- PO numbers can be added within 30 days of purchase
How to create this in 10 minutes
Step 1. Make sure your Product Management OS folder (second-pm-os) is open in Claude.
Step 2. In the chat panel, type:
/release-notes-pro mobile checkout redesign
Replace "mobile checkout redesign" with your feature name.
Step 3. Claude asks a few questions:
- What changed? — Describe the feature in plain language
- Who benefits? — Which users or segments care most
- How big is this launch? — Major announcement, minor update, or something in between
Step 4. Claude generates benefit-first release notes and saves them to:
launch/outputs/release-notes-pro-[feature].md
If something doesn't look right
Tell Claude what to change. For example:
- "Make it more casual — this is for our community Slack, not a press release"
- "Add a section about known limitations"
- "Create a short version I can use for an in-app banner (2 sentences max)"
- "Make it more technical — this is for the developer changelog"
- "Remove the emoji — our brand doesn't use them"
Pro tip
Ask Claude for multiple versions in one go: "Give me a changelog version, a customer email version, and a 2-line in-app banner." Claude will generate all three, each with the right tone and length.
What's next?
- Get Stakeholder Feedback — Review a document before sharing it widely
- Analyze a Competitor — Build a competitive profile in 10 minutes