Eol Message

Most product sunset announcements read like legal disclaimers or terse apologizes that tank customer trust. This gives you a nine-part framework for EOL messages that actually work: company context, clear announcement, customer-benefit rationale, honest impact assessment, transition solution, support measures, timeline, and next steps. It's built around empathy-first communication, meaning you acknowledge the disruption before justifying your decision. Use it when discontinuing products, sunsetting acquisitions, or migrating customers off legacy platforms. The framework is thorough, maybe overly so for simpler deprecations, but if you're shutting down something customers depend on, you need this level of rigor to prevent churn.

skills.sh installs: 2.6K
GitHub stars: 7.9K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add deanpeters/product-manager-skills --skill eol-message --agent claude-code

Installs into .claude/skills of the current project.

Files

EOL Message

Purpose

Craft a clear, empathetic End-of-Life (EOL) message that communicates discontinuation, explains the rationale, addresses customer impact, provides transition support, and positions what comes next. Use this to maintain customer trust during a difficult transition and reduce the churn that comes from customers feeling abandoned.

This is not a generic sunset announcement — it's a customer-centric communication that acknowledges loss while framing the change as progress. And it is sized to the change: a deprecated toggle gets a paragraph, a flagship retirement gets phased communications across months.

Input

Works best with: What's being retired (product, feature, or plan) and roughly when.

Also useful: The rationale, affected customer segments, migration or replacement path, support commitments, and any contract or regulatory language that constrains what you can say.

Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.

SKILL.md on GitHub