ga-announcement
Agent: PMM Analyst Content Strategist
L3 PMM analyst and content strategist (multi-instance) responsible for in-app announcements, changelog publishing, case study creation, and content engine operations.
Department ethos: ideal-product.md
Skill Description
Writes and distributes the general availability announcement for major releases, coordinating messaging across channels to maximize launch impact.
When to Use
- When a product or feature transitions from beta to general availability and requires a coordinated public announcement
- When a major version release ships and the company needs to communicate its significance to customers, prospects, and the market
- When a GA date is confirmed but no announcement draft, distribution plan, or stakeholder alignment exists yet
Workflow
- Gather launch context: Collect the PM launch brief, beta feedback summary, key metrics from the beta period, competitive positioning, and any customer quotes secured during beta. Confirm the GA date and embargo requirements. Deliverable: launch context document with all source materials and confirmed timeline.
- Define the messaging hierarchy: Identify the single headline message, three supporting proof points, and the primary call to action. Align with product, sales, and marketing leadership on positioning. Deliverable: approved messaging framework with headline, proof points, and CTA.
- Draft channel-specific announcements: Write the blog post (primary), email announcement, social media posts, and press release if applicable. Tailor length and tone to each channel while keeping the core message consistent. Deliverable: draft copy for each channel in the shared workspace.
- Coordinate cross-functional review: Route drafts to PM for accuracy, legal for compliance, sales for enablement alignment, and comms for brand voice. Resolve conflicting feedback and lock the final copy. Deliverable: approved final copy with sign-off from all reviewers.
- Execute the distribution sequence: Publish and distribute announcements in the planned sequence (blog first, then email, then social, then press). Confirm each channel fires on schedule. Deliverable: live announcements across all channels with distribution confirmation log.
- Measure and report: Track announcement performance (open rates, click-through, social engagement, press pickups) within the first 72 hours. Share a summary with the launch team. Deliverable: post-launch performance brief with metrics and observations.
Anti-Patterns
- Feature dump: Listing every change in the release instead of leading with the one story that matters to customers. Why: Announcements that read like release notes get skimmed; the headline impact is diluted and no single message sticks.
- Last-minute scramble: Starting the announcement draft after the GA date is already locked, leaving no time for review cycles. Why: Rushed copy contains errors, misses legal review, and forces stakeholders to approve under pressure, increasing reputational risk.
- Single-channel thinking: Writing only a blog post and treating it as the entire announcement. Why: Different audiences consume different channels; a blog-only approach misses prospects in email, social followers, and press readers.
Output
On success: A coordinated GA announcement published across blog, email, social, and press channels on schedule -- with a clear headline message, supporting proof points, customer quote, and call to action -- plus a 72-hour performance brief shared with the launch team.
On failure: Report which components stalled (missing approvals, delayed GA date, unavailable customer quote), what draft materials are ready, and recommend a revised distribution timeline or fallback messaging strategy.
Related Skills
case-study-extractor-pmm — sibling skill under the same agent — combine with case-study-extractor-pmm for end-to-end coverage
changelog-publisher-pmm — sibling skill under the same agent — combine with changelog-publisher-pmm for end-to-end coverage
content-engine-builder-pmm — sibling skill under the same agent — combine with content-engine-builder-pmm for end-to-end coverage
in-app-announcement-writer — sibling skill under the same agent — combine with in-app-announcement-writer for end-to-end coverage
partner-activation-planner-pmm — sibling skill under the same agent — combine with partner-activation-planner-pmm for end-to-end coverage
1---2name: ga-announcement3description: This skill writes and distributes the general availability announcement for major releases. Use when a product or feature moves from beta to GA and needs a coordinated external announcement. Also consider when a major release is approaching and no announcement draft exists yet. Suggest when the launch date is set but cross-functional teams have not aligned on messaging.4---56# ga-announcement78## Agent: PMM Analyst Content Strategist9L3 PMM analyst and content strategist (multi-instance) responsible for in-app announcements, changelog publishing, case study creation, and content engine operations.1011Department ethos: [ideal-product.md](../../../../departments/product/ideal-product.md)1213## Skill Description14Writes and distributes the general availability announcement for major releases, coordinating messaging across channels to maximize launch impact.1516## When to Use17- When a product or feature transitions from beta to general availability and requires a coordinated public announcement18- When a major version release ships and the company needs to communicate its significance to customers, prospects, and the market19- When a GA date is confirmed but no announcement draft, distribution plan, or stakeholder alignment exists yet2021## Workflow221. **Gather launch context**: Collect the PM launch brief, beta feedback summary, key metrics from the beta period, competitive positioning, and any customer quotes secured during beta. Confirm the GA date and embargo requirements. Deliverable: launch context document with all source materials and confirmed timeline.232. **Define the messaging hierarchy**: Identify the single headline message, three supporting proof points, and the primary call to action. Align with product, sales, and marketing leadership on positioning. Deliverable: approved messaging framework with headline, proof points, and CTA.243. **Draft channel-specific announcements**: Write the blog post (primary), email announcement, social media posts, and press release if applicable. Tailor length and tone to each channel while keeping the core message consistent. Deliverable: draft copy for each channel in the shared workspace.254. **Coordinate cross-functional review**: Route drafts to PM for accuracy, legal for compliance, sales for enablement alignment, and comms for brand voice. Resolve conflicting feedback and lock the final copy. Deliverable: approved final copy with sign-off from all reviewers.265. **Execute the distribution sequence**: Publish and distribute announcements in the planned sequence (blog first, then email, then social, then press). Confirm each channel fires on schedule. Deliverable: live announcements across all channels with distribution confirmation log.276. **Measure and report**: Track announcement performance (open rates, click-through, social engagement, press pickups) within the first 72 hours. Share a summary with the launch team. Deliverable: post-launch performance brief with metrics and observations.2829## Anti-Patterns30- **Feature dump**: Listing every change in the release instead of leading with the one story that matters to customers. *Why*: Announcements that read like release notes get skimmed; the headline impact is diluted and no single message sticks.31- **Last-minute scramble**: Starting the announcement draft after the GA date is already locked, leaving no time for review cycles. *Why*: Rushed copy contains errors, misses legal review, and forces stakeholders to approve under pressure, increasing reputational risk.32- **Single-channel thinking**: Writing only a blog post and treating it as the entire announcement. *Why*: Different audiences consume different channels; a blog-only approach misses prospects in email, social followers, and press readers.3334## Output35**On success**: A coordinated GA announcement published across blog, email, social, and press channels on schedule -- with a clear headline message, supporting proof points, customer quote, and call to action -- plus a 72-hour performance brief shared with the launch team.3637**On failure**: Report which components stalled (missing approvals, delayed GA date, unavailable customer quote), what draft materials are ready, and recommend a revised distribution timeline or fallback messaging strategy.3839## Related Skills40- [`case-study-extractor-pmm`](../case-study-extractor-pmm/SKILL.md) — sibling skill under the same agent — combine with case-study-extractor-pmm for end-to-end coverage41- [`changelog-publisher-pmm`](../changelog-publisher-pmm/SKILL.md) — sibling skill under the same agent — combine with changelog-publisher-pmm for end-to-end coverage42- [`content-engine-builder-pmm`](../content-engine-builder-pmm/SKILL.md) — sibling skill under the same agent — combine with content-engine-builder-pmm for end-to-end coverage43- [`in-app-announcement-writer`](../in-app-announcement-writer/SKILL.md) — sibling skill under the same agent — combine with in-app-announcement-writer for end-to-end coverage44- [`partner-activation-planner-pmm`](../partner-activation-planner-pmm/SKILL.md) — sibling skill under the same agent — combine with partner-activation-planner-pmm for end-to-end coverage