eol-message

Craft empathetic end-of-life announcements with rationale, impact, and next steps.

Updated Aug 18, 2024
One-click install
npx skills add https://github.com/ch-m-n/dotfile --skill eol-message-ch-m-n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eol-message
Source: https://github.com/ch-m-n/dotfile/tree/main/opencode/skills/eol-message
Command: npx skills add https://github.com/ch-m-n/dotfile --skill eol-message-ch-m-n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps customer-facing teams avoid confusion when retiring products, features, or plans by delivering a structured, empathetic EOL announcement that explains rationale, impact, and next steps.

Core Features & Use Cases

  • Empathy-first messaging framework: Guides you through company context, a clear announcement, customer-focused rationale, impact acknowledgment, and transition positioning before communicating change.
  • Transition planning guidance: Captures the current product context, outlines customer impact, defines the replacement solution, and lists support measures plus timeline milestones.
  • Use Case: When sunsetting a legacy API, follow the template to acknowledge disruption, explain the new platform, and offer migration support so customers retain trust.

Quick Start

Use the eol-message skill to draft an empathetic EOL announcement that states the rationale, customer impact, transition support, 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 retired product?

An empathetic end-of-life announcement explains discontinuations with clarity by structuring company context, customer-focused rationale, impact acknowledgment, transition support, and timeline milestones to build trust during product transitions.

What should be included in a product sunset planning communication to customers?

Product sunset planning communications should include a clear announcement, rationale for discontinuation, acknowledgment of customer impact, replacement solution positioning, defined support measures, and actionable next steps.

How do I structure an EOL announcement that explains a legacy API deprecation?

Structure an EOL announcement by acknowledging disruption, explaining the new replacement platform, and offering migration support with timeline milestones so customers retain trust during the API transition.

What is the best way to communicate product transition support to affected users?

The best way to communicate product transition support is through an empathy-first messaging framework that captures current product context, outlines customer impact, and lists support measures and timeline milestones.

When do I need a structured EOL announcement framework for sunsetting a feature?

You need a structured EOL announcement framework when retiring products, features, or plans to avoid customer confusion and deliver a clear communication covering rationale, impact, and next steps.