eol-message

Generate structured end-of-life messages for discontinued products or features.

6.4k|767|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill eol-message
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eol-message
Source: https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-message
Command: npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill eol-message

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Craft a clear, empathetic End-of-Life (EOL) message that communicates product or feature discontinuation, explains the rationale, addresses customer impact, provides transition support, and positions the replacement solution. Use this to maintain customer trust during difficult transitions and reduce churn by demonstrating care and offering a clear path forward.

Core Features & Use Cases

  • Structured messaging framework: Includes sections for company context, the announcement, the rationale, current product context, customer impact, transition solution, differentiation, support measures, and timeline.
  • Customer-centric tone: Emphasizes honesty, empathy, and support to minimize disruption and preserve relationships.
  • Use cases: Ideal for sunsetting products or APIs, migrating customers to replacements, and communicating data export or transition plans.
  • Example workflow: Drafts a complete EOL notice with a multi-month timeline, migration assistance, and clear calls to action.

Quick Start

  • Provide the product name being discontinued, the planned date, and the replacement or migration plan; then request a complete EOL message draft covering all sections.

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 message for a discontinued product?

Write an end-of-life message by structuring the announcement with company context, rationale, customer impact, transition support, and a clear timeline. This ensures the communication preserves customer trust while providing a clear path forward.

What should a product discontinuation notice include to minimize customer churn?

A product discontinuation notice should include the rationale, current product context, transition solution, differentiation, support measures, and a call to action. This empathetic framework minimizes churn by demonstrating care and offering clear migration assistance.

How do I communicate a sunsetting timeline to customers transitioning to a replacement?

Communicate a sunsetting timeline by drafting a multi-month schedule that details migration assistance and clear calls to action. This structured approach addresses customer impact and provides transition support across all communications channels.

When should I use a structured EOL messaging framework for feature deprecation?

Use a structured EOL messaging framework when sunsetting products or APIs, migrating customers to replacements, and communicating data export or transition plans. It enforces a structured narrative that maintains honesty and empathy during difficult transitions.

Can I use this EOL communication approach for API deprecation and data export plans?

Yes, you can use this EOL communication approach for API deprecation and data export plans. It drafts complete notices covering announcements, customer impact, transition solutions, and support measures specifically designed for these technical migrations.

Does an empathetic end-of-life message really preserve customer trust during product transitions?

An empathetic end-of-life message preserves customer trust by emphasizing honesty and support to minimize disruption. It addresses customer impact directly while positioning the replacement solution and offering clear transition assistance.