SkillsAdd

pavloglushko/ai-skills · Archived

pavlo-release-announcer

Generates non-technical Slack announcements for end users based on ticket, commits, and plan. Use after Phase 3 when you're ready to communicate the release to non-technical stakeholders.

Installation

$ npx skills add pavloglushko/ai-skills --skill pavlo-release-announcer
View on skills.sh ↗ GitHub repository ↗

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

pavlo-markdown-editor Same source · more installs
pavloglushko/ai-skills

Create, edit, and reformat Markdown files following strict line-length and meaning-boundary wra…

30 installs
pavlo-jira-ticket-writer Same source · more installs
pavloglushko/ai-skills

Write structured engineering tickets for Jira, output as .md files ready to paste into a Jira t…

29 installs
pavlo-commit-by-commit-execution Same source
pavloglushko/ai-skills

Systematic approach to implementing multi-step plans with explicit user confirmation between ea…

28 installs
pavlo-commit-rewriter Same source
pavloglushko/ai-skills

Automates Phases 1–3 of the commit rewriting workflow: preparation, analysis & message drafting…

27 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

ln-912-community-announcer Similar name
levnikolaevich/claude-code-skills

Composes and publishes announcements to GitHub Discussions. Use when sharing releases, updates,…

185 installs

Also in this package

Other skills from pavloglushko/ai-skills.

npx skills add pavloglushko/ai-skills
pavlo-markdown-editor 30 pavlo-jira-ticket-writer 29 pavlo-commit-by-commit-execution 28 pavlo-commit-rewriter 27 pavlo-commit-oriented-planning 26 pavlo-agent-skill-creator 26 pavlo-marp-presentation 16

Browse all from pavloglushko/ai-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License LICENSE
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.1.0
More metadata
author
Pavlo Glushko
version
1.1.0
applies_to
["**\/.github\/skills\/pavlo-release-announcer\/**"]
triggers
["rewrite commits phase 4","slack announcement","user announcement","end user communication","slack message","release announcement"]
capabilities
["gather context from ticket and plan","synthesize user-visible changes","generate non-technical Slack messages","ask for affected users, activation date, contact info","use Slack emoji markers for structure","present announcements via show_content tool"]

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,558 B
  • docs SUMMARY.md 218 B

History

  1. First recorded snapshot · 28 installs

SKILL.md

Skill: Release Announcer

Generates a non-technical Slack announcement for end users based on the ticket, commits, and plan. Translates internal implementation details into user-visible changes in plain English.

When to Use

After completing PR message generation (PR Writer skill), when you're ready to communicate the release to non-technical stakeholders (end users, ops team, business stakeholders). Typically posted to Slack channels after merge.

Process Overview

  1. Ask for context from user:

- Who is affected (e.g., end users, ops team, business stakeholders) - Activation date (e.g., "immediately after merge", specific date) - Contact person for questions

  1. Synthesize from ticket/plan/commits:

- What is the user-visible problem being solved? - What is the user-visible solution (what changed for them)? - What should they be aware of?

  1. Generate Slack announcement using the standard template (see below)
  1. Present to user via show_content tool in Markdown format

Slack Announcement Template

**ANNOUNCEMENT: <short user-facing title> (<team / domain>)**

:office_worker: Affected (external) users: <who is affected, e.g., end users, ops team>

Type / Category of release: <New feature | Bug fix | Improvement>

:large_orange_diamond: Description of change:
**Problem:** <1–3 sentences in plain language>

**Solution:** <1–3 sentences describing what changed from the user's perspective>

:spiral_calendar_pad: Activation date: <date or "after merge">

:telephone_receiver: Contact person/s: <names>

:warning: Please note
<any caveats, limitations, or things users should be aware of>

Key Guidelines

  • No code references: Avoid class names, method names, config keys, or file paths
  • Plain English: Assume audience is non-technical (they use the product, read reports, don't care about architecture)
  • User perspective: Focus on "what changed for me?" not "what changed in the code?"
  • Brevity: Entire message should fit in one Slack post without scrolling
  • Emojis: Use provided emoji markers for visual structure (:officeworker:, :largeorange_diamond:, etc.)

Implementation Notes

  • Translate technical changes to user-facing impact (e.g., "Added validation logic" → "The system will now reject invalid input with a clear error message")
  • Ask user if affected parties and activation date are not obvious from context
  • Verify the announcement is understandable to someone unfamiliar with the codebase
  • Use show_content with format name slack-announcement.md

Related

  • PR Writer skill provides the technical PR description to synthesize from
  • Commit Rewriter skill provides the commits and changes