Start with the source and its limits
Use the release note, product decision, changelog, or owner-approved source as the record of what changed. Do not promote a claim that the source does not support.
- Keep the source link or note beside the draft.
- Name what changed and who it helps.
- Mark claims that need a product owner or technical review.
Choose one reader outcome
A release is not automatically a useful social post. Choose the most relevant reader consequence, then explain it with the context that keeps the claim accurate.
- Write the reader outcome in one sentence.
- Remove implementation detail that does not help that reader.
- Keep any important qualification beside the benefit.
Adapt the source for each platform
Preserve the evidence while changing the opening, structure, and level of context for X and LinkedIn. Do not turn a product note into identical cross-posts by default.
- Write a platform-specific opening.
- Check X length, links, and media before review.
- Keep source details available for readers who need them.
Approve the exact publication bundle
Review the final text, account, media, links, source context, date, time, and timezone together. A later meaningful edit should return the post to review.
- Record the revision being approved.
- Schedule only the approved version.
- Verify the destination record or failure state after delivery.
A final quality check
- The source supports every material claim.
- The post explains one reader-relevant outcome.
- X and LinkedIn versions are adapted rather than duplicated.
- The exact text, account, media, links, and schedule are reviewed together.
- The published record or failure state is checked after delivery.
Questions about this skill
- Should every product update become a social post?
- No. Share updates with a clear reader consequence and enough source material to explain the claim accurately. Keep routine internal changes in the source record when they do not create a useful audience update.
- Can I use the same release-note wording on every platform?
- Keep the facts consistent, but adapt the opening and context for the platform and reader. The exact approved version should be stored with its destination and schedule.
- What should be reviewed before scheduling a product update?
- Review the source, exact text, material claims, account, media, links, date, time, timezone, and the revision that will be published.
Put the skill to work
Bring the idea. LaunchPost helps shape the draft.
Use your own business context, voice, and source material to move from an idea to content ready for review.
Open LaunchPost