eol-message
Write a clear, empathetic EOL announcement with rationale, customer impact, and next steps. Use when retiring a product, feature, or plan without creating avoidable confusion.
npx skills add deanpeters/Product-Manager-Skills --skill eol-message --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
## Purpose 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. This is not a generic sunset announcement—it's a customer-centric communication that acknowledges loss while framing the change as progress. ## 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, and support commitments. 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. **Arriving empty-handed? That works too.** The skill asks for the what/when/why before drafting — an EOL message without a stated rationale and next step reads as abandonment. **Example invocation:** `Draft an EOL message: retiring our legacy reporting mo
- Purpose
- Input
- Key Concepts
- The EOL Messaging Framework
- Why This Works
- Anti-Patterns (What This Is NOT)
- When to Use This
- When NOT to Use This
- Application
- Step 1: Gather Context
- Step 2: Draft the Product Transition Narrative
- Step 3: Provide Current Product Context
- Step 4: Acknowledge Customer Impact
- Step 5: Present the Transition Solution
What does the eol-message skill do?
Write a clear, empathetic EOL announcement with rationale, customer impact, and next steps. Use when retiring a product, feature, or plan without creating avoidable confusion.
How do I install it?
Run `npx skills add deanpeters/Product-Manager-Skills --skill eol-message --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From deanpeters/Product-Manager-Skills, a repository with 6,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.