For developer-facing release notes where clarity prevents breakage.
Given these changes: [paste], write technical release notes for developers. Group by type (breaking, feature, fix). Include migration steps for breaking changes.
Anything in square brackets is meant to be replaced. The builder turns those into fields you can type into.
Tired of re-pasting the same context into every new chat? That is what the Unimatrix MCP server is for.