eol-message

Write empathetic end-of-life announcements with timelines and transition guidance.

358|11|Updated May 15, 2026
One-click install
npx skills add https://github.com/getcrew44/crew44 --skill eol-message-getcrew44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eol-message
Source: https://github.com/getcrew44/crew44/tree/main/daemon/internal/presets/defaultcrew/skills/product/eol-message
Command: npx skills add https://github.com/getcrew44/crew44 --skill eol-message-getcrew44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you write a clear, empathetic end-of-life (EOL) announcement that explains what’s ending, why it’s happening, how customers will be affected, and what they should do next—reducing confusion and churn during difficult transitions.

Core Features & Use Cases

  • Customer-centric EOL messaging: Communicates discontinuation with empathy, clarity, and respect for the customer relationship.
  • Rationale and impact that match reality: Explains the decision with customer-benefit framing and acknowledges disruption honestly.
  • Actionable transition guidance: Includes a replacement/next solution, support measures, a timeline, and concrete call-to-action steps.
  • Use case: Retiring a product, feature, or plan and migrating customers to a successor solution with documented milestones and support.

Quick Start

Draft an EOL announcement for retiring Product X on December 31, 2026, migrating customers to Product Y, including the rationale, customer impact, support measures, and a specific timeline with next steps and contact information.

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 that reduces customer churn?

An effective end-of-life announcement reduces churn by combining empathetic discontinuation messaging with a customer-benefit-focused rationale, explicit timeline milestones, transition support details, and a clear call to action.

What should be included in an EOL announcement for retiring a product feature?

An EOL announcement for retiring a feature must include the discontinuation rationale, honest acknowledgment of customer impact, transition guidance to a replacement solution, support measures, and concrete next steps.

How do I communicate product retirement timeline milestones to customers?

Communicate product retirement timeline milestones by documenting explicit dates for discontinuation, outlining migration phases to the successor solution, and detailing available support measures throughout the transition.

What is the best way to write migration messaging for customers moving to a replacement solution?

The best way to write migration messaging is to frame the transition around customer benefits, provide actionable guidance for adopting the successor solution, and include a specific call to action with support contact information.

Does this approach work for retiring APIs and service plans, or just full products?

This EOL announcement approach works for retiring full products, individual features, service plans, and APIs, applying customer-centric empathy and transition support across all customer-impact scenarios.

Why does customer communication matter when discontinuing support for legacy products?

Customer communication matters during discontinuation because clearly explaining the rationale, impact, and next steps preserves customer trust and reduces confusion during difficult migration transitions.