eol-message

Generate empathetic End-of-Life messages for product or feature discontinuation.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/Johnnnmai/100x-product-manager --skill eol-message-johnnnmai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eol-message
Source: https://github.com/Johnnnmai/100x-product-manager/tree/main/skills/eol-message
Command: npx skills add https://github.com/Johnnnmai/100x-product-manager --skill eol-message-johnnnmai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you create clear, empathetic End-of-Life (EOL) messages for products or features, ensuring customer trust during transitions and minimizing churn.

Core Features & Use Cases

  • Structured Messaging: Provides a framework for all essential EOL communication components.
  • Customer-Centric Rationale: Guides you to explain the "why" from the customer's benefit perspective.
  • Use Case: You need to announce the discontinuation of a legacy software feature. This Skill will help you draft a message that explains the change, details the replacement, outlines support, and provides a clear timeline, all while acknowledging customer impact.

Quick Start

Use the eol-message skill to draft an end-of-life announcement for the 'Legacy Dashboard' feature.

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 empathetic end-of-life message for a product sunset?

An empathetic product sunset message explains the rationale from the customer's perspective, acknowledges the impact, details transition support, and outlines a clear timeline to maintain trust and minimize churn.

What should be included in a product discontinuation announcement to reduce customer churn?

A product discontinuation announcement should include a customer-centric rationale, a clear transition timeline, details on replacement solutions, and available support options to ensure customer retention during the lifecycle change.

What is the best way to communicate a legacy feature EOL to existing users?

The best way to communicate a legacy feature EOL is structuring the message to explain the change, outline replacement solutions, and provide transition support, ensuring the communication remains empathetic and clear.

How do I structure transition planning communication for a product being discontinued?

Structure transition planning communication by explaining the discontinuation rationale, addressing customer impact, offering transition support, and positioning replacement solutions to guide users smoothly through the product lifecycle change.

Does an EOL message need to detail replacement solutions for the discontinued product?

Yes, an EOL message must detail replacement solutions. Positioning the replacement within the discontinuation announcement helps maintain customer trust and provides a clear path forward during the product transition.