EOL Internal Enablement

Purpose

Build what customer-facing teams need before the EOL announcement goes out: a support FAQ, sales talking points with honest comparison data, objection handling, an escalation ladder, and, when the sunset warrants it, a channel partner brief and a training outline.

The cardinal sin of EOL communication is handing Support and Sales the announcement five minutes before customers get it and wishing them luck. This skill exists to prevent that. Internal readiness is a prerequisite for announcing, not a follow-up task.

Input

Works best with: The product being sunset, what replaces it (if anything), and the key dates.

Also useful: The objections you expect, which accounts are at risk, what continues versus what stops, and whether channel partners are in the picture.

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 up to three questions, what's being sunset and what replaces it, the dates for stopping sale/support/service, and the top objections you expect, then builds the pack. If you don't know the objections, it drafts the predictable ones and you edit.

Example invocations:

• Build the enablement pack for our legacy module sunset, replaced by the new dashboard, EOL Dec 31.
• Support FAQ only, feature deprecation, no replacement, three weeks notice.

---

Key Concepts

Right-Size the Pack

Not all EOLs play out the same. Most land in the middle: