eol-message

Craft empathetic end-of-life announcements with rationale, impact, and transition support.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nv-minh/superpower-agent --skill eol-message-nv-minh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eol-message
Source: https://github.com/nv-minh/superpower-agent/tree/main/templates/base/Product-Manager-Skills/skills/eol-message
Command: npx skills add https://github.com/nv-minh/superpower-agent --skill eol-message-nv-minh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents clumsy sunset announcements by guiding you through an empathetic, customer-forward EOL communication that explains why a product, feature, or service is retiring without causing unnecessary confusion or distrust.

Core Features & Use Cases

  • Structured Messaging Framework: Provides company context, announcement, rationale, customer impact, transition solution, support measures, timeline, and call to action so every EOL message is complete.
  • Guided Narrative: Includes guidance on framing empathy, impact, and continuity, plus templates and examples for product managers handling major retirements.
  • Use Case: Use it when migrating customers from a legacy platform to a replacement so they know what’s changing, why it matters, and how to move forward.

Quick Start

Use the template to draft an empathetic EOL announcement covering context, rationale, impact, transition plan, support, timeline, and next steps.

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 announcement for a product retirement?

An empathetic end of life announcement requires a structured framework covering company context, rationale, customer impact, transition solutions, support measures, timeline, and a clear call to action. This approach maintains customer trust during product retirements.

What should a product sunset communication include to manage customer expectations?

A product sunset communication should include the discontinuation rationale, specific customer impact details, a viable transition solution, ongoing support plans, and a clear migration timeline. Structuring these elements prevents confusion and distrust.

How do I announce a feature sunset without causing customer churn?

To announce a feature sunset without causing churn, frame the messaging with empathy and continuity. Clearly explain the retirement rationale, outline a seamless transition path to a replacement, and provide dedicated support throughout the migration timeline.

What is the best way to communicate a legacy platform migration to existing users?

The best way to communicate a legacy platform migration is a guided narrative that explicitly states what is changing, why it matters to the user, and how to move forward using a structured template covering transition plans and support.

Can I use a template for drafting EOL messaging for discontinued services?

Yes, you can use a structured EOL messaging template to draft discontinuation announcements. It guides you through framing empathy, impact, and continuity, ensuring every draft includes the rationale, transition plan, and next steps.