# Eol Stakeholder Sequence

Plan who to talk to about a sunset, in what order, and what each conversation must cover.

- Repository: https://github.com/deanpeters/Product-Manager-Skills (7825 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-10-16
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## Description

Plan who to talk to about a sunset, in what order, and what each conversation must cover. Use when an EOL decision is made and you want the landmines found before the announcement.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# EOL Stakeholder Sequence

## Purpose

Plan the order of EOL conversations, and what each one must cover. The output is a sequenced list of
stops, each with what you need **from** them, what you owe **to** them, the red flags to listen
for, and what the conversation must produce.

EOL is not a broadcast. It is a series of conversations where each one informs the next, and each
one surfaces something the last one missed. Sequenced well, the awkward discoveries happen in a
conference room. Sequenced badly, they happen in public, after the announcement, in front of
customers.

## Input

**Works best with:** The product being sunset and who already knows about it.

**Also useful:** Scale (customers, revenue, contracts), whether channel partners or regulators are
involved, and any political sensitivities, strained relationships, or past surprises worth planning
around.

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 who knows, how big the blast radius is, and whether there's history to plan around, then builds the sequence. Political sensitivities are optional; the sequence works without them and
sharpens with them.

**Example invocations:**
- `Sequence the stakeholder conversations for retiring our legacy reporting module.`
- `Who do I talk to, in what order, about sunsetting a hardware line with 8 resellers?`

---

## Key Concepts

### The Sequencing Principle

**Talk to the people who can kill the plan before you talk to the people who have to execute it.**

The rest: https://github.com/deanpeters/Product-Manager-Skills/blob/HEAD/skills/eol-stakeholder-sequence/SKILL.md