Release Title

Month Day, Year

One or two sentences, in second person, that answer: what is this and why would you use it today? Lead with the user outcome, not the internal reason we built it.

What you can do

• concrete capability with specifics (names, numbers, limits)
• concrete capability with specifics
• list every meaningful thing the feature lets the user do — don't abbreviate the capability list
• if there are sub-tools or tasks, name them

Where this shows up

Concrete scenarios in your voice. "You want X. You used to have to Y. Now you just Z." Pick two or three real moments where someone would actually hit this.

Try it

• "prompt you'd paste into Alfrada"
• "another concrete prompt"
• "one more — ideally showing a different angle"

Heads up

Only include this section when there's something the user genuinely needs to know: pricing change, breaking behaviour, back-fill rules, limits, migration steps. Delete the whole section if there's nothing to flag.