Product release recipe

Create credible release content from repository evidence.

1
Choose the evidence
Point the agent to the release tag, changelog, migration guide and relevant commits.
2
Name the reader
Separate current users who need action from prospects who need context.
3
Set claim boundaries
Require the agent to ask before using metrics, comparisons or customer outcomes.
4
Submit, do not publish
Create canonical Markdown and a destination-native Run, then stop for human review.

Release prompt

Use the Postward MCP to create a campaign and submit its first content package for review.
Source of truth: inspect this repository's changelog, release notes and recent changes.
Objective: explain what shipped and why it matters to existing users.
Audience: developers evaluating or already using the product.
Destinations: LinkedIn and Discourse.
Before writing, ask only for decisions or facts that are genuinely missing.
Create canonical Markdown first, then generate destination-native materializations from that exact source revision and submit a Run.
Do not invent claims, metrics or customer evidence. Do not approve, schedule or publish.

Review and publish