eol-stakeholder-sequence
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.
Profile →npx skills add deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence --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.
# 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 kn
- Purpose
- Input
- Key Concepts
- The Sequencing Principle
- Right-Size the Sequence
- The Canonical Order
- Why Your Most Difficult Customers Belong in the Sequence
- What You Need / What You Owe
- The Sticky-Note Rule
- Anti-Patterns (what this is NOT)
- Application
- Step 1: Set the level
- Step 2: Order the stops
- Step 3: Build each stop
What does the eol-stakeholder-sequence skill do?
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.
How do I install it?
Run `npx skills add deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence --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,444 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.