eol-message

Create empathetic end-of-life announcements for product or feature discontinuations.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/omeragaakbas/zoyare --skill eol-message-omeragaakbas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eol-message
Source: https://github.com/omeragaakbas/zoyare/tree/main/.claude/skills/eol-message
Command: npx skills add https://github.com/omeragaakbas/zoyare --skill eol-message-omeragaakbas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams avoid confusion and churn when retiring a product, feature, or plan by providing an empathy-first, structured announcement that explains the rationale, acknowledges customer impact, and outlines clear next steps and support.

Core Features & Use Cases

  • Empathy-first framework: Guides you to acknowledge disruption before presenting the business rationale.
  • Structured announcement sections: Company context, announcement, rationale, product context, customer impact, transition solution, support measures, timeline, and call to action.
  • Templates and examples: Ready-to-fill template and sample messages for product managers, customer success, and communications teams.
  • Use cases: Sunsetting legacy features, migrating customers to a new platform, deprecating APIs, or consolidating product plans.

Quick Start

Write an empathetic end-of-life announcement for the product that states what is ending, why, who is affected, key dates, available migration support, and a clear call to action.

Frequently Asked Questions about eol-message

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an end-of-life announcement for retiring a product?

A product sunset announcement requires an empathy-first framework that acknowledges disruption before presenting business rationale, covering company context, customer impact, transition solutions, support measures, and timeline.

What should be included in a product sunset messaging template?

A product sunset messaging template should include structured sections for announcement, rationale, product context, customer impact, transition solution, support measures, timeline, and a clear call to action.

How do I communicate a feature deprecation to affected user segments?

Communicating feature deprecation requires identifying affected user segments, explaining the discontinuation rationale, and outlining available migration support and key dates across channels like email, customer portals, and release notes.

Can I use this framework for migrating customers to a new platform?

Yes, this framework supports migrating customers to a new platform by generating actionable copy that details replacement options, timeline milestones, and available support measures for the transition.

What is the best way to announce an API deprecation to customers?

The best way to announce an API deprecation is to use a structured, empathy-first announcement that clearly states what is ending, who is affected, key timeline milestones, and available migration paths.