Release Announcements

Generate and post release announcements to Slack, Discord, and X from changelog entries. Uses three different models across three phases: draft (gemini-3-flash-preview), critique (gpt-5.2), and improve (claude-opus-4.5).

Inputs

version

Version number to announce (e.g., "1.0.0").

• type: string
• required: true

changelog_path

Path to CHANGELOG.md file.

• type: string
• required: true

slack_channel

Slack channel name (without #).

• type: string
• required: true

discord_channel_id

Discord channel ID for posting.

• type: string
• required: true

github_owner

GitHub repository owner.

• type: string
• required: false
• default: "spinje"

github_repo

GitHub repository name.

• type: string
• required: false
• default: "pflow"

output_dir

Directory to save X post file.

• type: string
• required: false
• default: "."

Steps

read-changelog

Read the changelog file content.

• type: read-file
• file_path: ${changelog_path}

extract-changelog-section

Extract the changelog section for the specified version.

• type: code
• inputs: content: ${read-changelog.content} version: ${version}

pythoncontent: str
version: str
import re

pattern = rf"## v{re.escape(version)}.*?\n(.*?)(?=\n## v|\Z)"
match = re.search(pattern, content, re.DOTALL)
if match:
    result: str = match.group(1).strip()
else:
    result: str = ""

draft-announcements

Draft release announcements for all three platforms using gemini-3-flash-preview.

• type: llm
• model: gemini-3-flash-preview

yamlitems:
  - platform: slack
    format_rules: |
      Slack format:
      - Markdown: *bold*, \`code\`
      - Link: github.com/${github_owner}/${github_repo}/releases/tag/v${version} (must be release URL, not just repo)
      - No forced jokes
  - platform: discord
    format_rules: |
      Discord format:
      - Markdown: **bold**, \`code\`
      - Link: github.com/${github_owner}/${github_repo}/releases/tag/v${version} (must be release URL, not just repo)
      - No quirky filler
  - platform: x
    format_rules: |
      X (Twitter) format - DIFFERENT rules:
      - 280 characters max
      - Line breaks required between sections (not one long line)
      - Focus on the most interesting/impactful feature from changelog; avoid overly technical fixes
      - Feature mentioned must be specific, not generic
      - Exact format:
        [project] [version] tagged.

        [one key feature sentence]

        Ask @grok to read github.com/${github_owner}/${github_repo}/blob/main/releases/v${version}-context.md and explain [specific feature from changelog]
      - Link rules (different from Slack/Discord):
        - Uses /blob/main/releases/v[VERSION]-context.md (NOT /releases/tag/)
        - The @grok CTA is the link - do NOT add a separate GitHub release link
parallel: true

promptYou are drafting a release announcement for ${item.platform}.

Project: ${github_repo}
Version: ${version}
Changelog:
${extract-changelog-section.result}

${item.format_rules}

Voice guidelines:
- Tone: "tired-but-competent engineer" - low-ego, high-signal, no hype
- Better rough and real than polished and generic
- No lame or generic fillers (no coffee mentions, no "exciting", no "we're thrilled")
- Avoid: hustle-bro energy, VC-speak, "game changer" language, inspirational poster vibes, "building the future" startup tone

Write ONLY the announcement text. No explanations, no meta-commentary.

critique-announcements

Critique each draft using gpt-5.2.

• type: llm
• model: gpt-5.2

yamlitems:
  - platform: slack
    draft: ${draft-announcements.results[0].response}
    format_rules: |
      Slack format:
      - Markdown: *bold*, \`code\`
      - Link: github.com/${github_owner}/${github_repo}/releases/tag/v${version} (must be release URL, not just repo)
      - No forced jokes
  - platform: discord
    draft: ${draft-announcements.results[1].response}
    format_rules: |
      Discord format:
      - Markdown: **bold**, \`code\`
      - Link: github.com/${github_owner}/${github_repo}/releases/tag/v${version} (must be release URL, not just repo)
      - No quirky filler
  - platform: x
    draft: ${draft-announcements.results[2].response}
    format_rules: |
      X (Twitter) format - DIFFERENT rules:
      - 280 characters max
      - Line breaks required between sections (not one long line)
      - Focus on the most interesting/impactful feature from changelog; avoid overly technical fixes
      - Feature mentioned must be specific, not generic
      - Exact format:
        [project] [version] tagged.

        [one key feature sentence]

        Ask @grok to read github.com/${github_owner}/${github_repo}/blob/main/releases/v${version}-context.md and explain [specific feature from changelog]
      - Link rules (different from Slack/Discord):
        - Uses /blob/main/releases/v[VERSION]-context.md (NOT /releases/tag/)
        - The @grok CTA is the link - do NOT add a separate GitHub release link
parallel: true

promptYou are critiquing a ${item.platform} release announcement.

Draft:
${item.draft}

Original changelog:
${extract-changelog-section.result}

Platform format requirements (immutable - these CANNOT be changed):
${item.format_rules}

Review criteria:
1. Validate compliance with Platform Formats (correct markdown, correct link format, X char count and structure)
2. Flag voice violations (should be "tired-but-competent engineer" - low-ego, high-signal, no hype)
3. Check for hallucinated information (all info must come from the changelog)
4. Suggest deeper content improvements (not just checkbox validation)

IMPORTANT: Do not suggest structural changes that violate Platform Formats (e.g., do not suggest removing the @grok CTA or adding a separate GitHub link to X). Format requirements take precedence.

Provide specific, actionable feedback.

improve-announcements

Apply improvements using claude-opus-4.5.

• type: llm
• model: claude-opus-4.5

yamlitems:
  - platform: slack
    draft: ${draft-announcements.results[0].response}
    critique: ${critique-announcements.results[0].response}
    format_rules: |
      Slack format:
      - Markdown: *bold*, \`code\`
      - Link: github.com/${github_owner}/${github_repo}/releases/tag/v${version} (must be release URL, not just repo)
      - No forced jokes
  - platform: discord
    draft: ${draft-announcements.results[1].response}
    critique: ${critique-announcements.results[1].response}
    format_rules: |
      Discord format:
      - Markdown: **bold**, \`code\`
      - Link: github.com/${github_owner}/${github_repo}/releases/tag/v${version} (must be release URL, not just repo)
      - No quirky filler
  - platform: x
    draft: ${draft-announcements.results[2].response}
    critique: ${critique-announcements.results[2].response}
    format_rules: |
      X (Twitter) format - DIFFERENT rules:
      - 280 characters max
      - Line breaks required between sections (not one long line)
      - Focus on the most interesting/impactful feature from changelog; avoid overly technical fixes
      - Feature mentioned must be specific, not generic
      - Exact format:
        [project] [version] tagged.

        [one key feature sentence]

        Ask @grok to read github.com/${github_owner}/${github_repo}/blob/main/releases/v${version}-context.md and explain [specific feature from changelog]
      - Link rules (different from Slack/Discord):
        - Uses /blob/main/releases/v[VERSION]-context.md (NOT /releases/tag/)
        - The @grok CTA is the link - do NOT add a separate GitHub release link
parallel: true

promptYou are improving a ${item.platform} release announcement.

Original draft:
${item.draft}

Critique feedback:
${item.critique}

Source changelog (for accuracy verification):
${extract-changelog-section.result}

Platform format requirements (IMMUTABLE - these MUST be preserved):
${item.format_rules}

Instructions:
1. Apply valid content suggestions from critique
2. REJECT any critique suggestions that violate Platform Formats (format requirements take precedence over critique)
3. Verify accuracy against source changelog
4. Maintain voice: "tired-but-competent engineer" - low-ego, high-signal, no hype

Output ONLY the final announcement text for ${item.platform}. No explanations, no meta-commentary.

post-to-slack

Post the improved Slack announcement.

• type: mcp-composio-slack-SLACK_SEND_MESSAGE
• channel: ${slack_channel}
• markdown_text: ${improve-announcements.results[0].response}

post-to-discord

Post the improved Discord announcement.

• type: mcp-discord-execute_action
• server_name: discord
• category_name: DISCORD_CHANNELS_MESSAGES
• action_name: create_message
• path_params: channel_id: ${discord_channel_id}
• body_schema: content: ${improve-announcements.results[1].response}

save-x-post

Save the X post to a file for human review before posting.

• type: write-file
• file_path: ${output_dir}/x-post-v${version}.txt
• content: ${improve-announcements.results[2].response}

generate-summary

Generate a summary of what was posted.

• type: code
• inputs: version: ${version} slack_channel: ${slack_channel} discord_channel_id: ${discord_channel_id} x_file_path: ${output_dir}/x-post-v${version}.txt slack_post: ${improve-announcements.results[0].response} discord_post: ${improve-announcements.results[1].response} x_post: ${improve-announcements.results[2].response}

pythonversion: str
slack_channel: str
discord_channel_id: int
x_file_path: str
slack_post: str
discord_post: str
x_post: str

summary = f"""Release Announcements Summary for v{version}
{'=' * 50}

POSTED:
- Slack: #{slack_channel}
- Discord: channel {discord_channel_id}

SAVED FOR REVIEW:
- X post: {x_file_path}

---
SLACK ANNOUNCEMENT:
{slack_post}

---
DISCORD ANNOUNCEMENT:
{discord_post}

---
X POST (pending human review):
{x_post}
"""

result: str = summary

Outputs

summary

Summary of posted announcements and saved X post.

• source: ${generate-summary.result}