eol-stakeholder-sequence

Plan the order and content of stakeholder conversations for a product end-of-life decision.

6.8k|818|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eol-stakeholder-sequence
Source: https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/eol-stakeholder-sequence
Command: npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a product sunset is announced before the right internal conversations happen, contract terms, field promises, and hidden dependencies surface publicly instead of in a conference room. This Skill sequences EOL stakeholder conversations so legal exposure, financial impact, and customer risks are found before the announcement, not after.

Core Features & Use Cases

  • Sequenced conversation plan: Produces an ordered list of stakeholder stops, each with what you need from them, what you owe them, red flags to watch for, and the output the conversation must produce.
  • Right-sized scoping: Offers three levels (Light, Standard, Heavy) matched to blast radius, from a feature deprecation to a regulated hardware sunset, so the plan fits the stakes.
  • Parallel vs. sequential guidance: Marks which stops have hard dependencies and which can run concurrently to compress the timeline safely.
  • Use Case: You are retiring a SaaS product with 800 accounts and annual contracts. The Skill produces an eight-stop sequence starting with Legal and Finance, asking Sales what was promised before telling them the date, and briefing your most difficult customers under NDA before the public announcement.

Quick Start

Ask the AI to sequence the stakeholder conversations for sunsetting your product, including who already knows and how large the customer and revenue impact is.

Frequently Asked Questions about eol-stakeholder-sequence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan stakeholder communication for a product end-of-life?

Sequence conversations so each informs the next: Legal first for contract exposure, Finance for revenue impact, then Sales, Marketing, Customer Success, and difficult customers before any announcement. Each stop should define what you need from them, what you owe them, and the decision it must produce.

Who should I talk to first when sunsetting a product?

Talk to Legal first for any commercial product with contracts, because a contract term can invalidate the entire plan. Finance comes second to size the revenue impact, then revenue-facing and customer-facing teams, with technical teams carrying out execution.

How many stakeholder conversations does a product sunset require?

It depends on blast radius: a feature or internal tool needs 3-4 stops, a commercial product with paying customers needs 7-8, and revenue-critical, hardware, or regulated products need 10 or more including executives, channel partners, and regulators.

Why should difficult customers be consulted before an EOL announcement?

Your most demanding customers have the deepest and most unusual product usage, so they surface forgotten integrations, unread contract terms, and workflows with no replacement equivalent. Learning this in a scheduled call under NDA beats learning it on a public forum after the announcement.

What is the difference between a stakeholder sequence and a stakeholder map?

A stakeholder map plots power and interest to prioritize engagement, while a stakeholder sequence is an ordered itinerary of conversations where each one informs the next. This Skill produces the sequence, not a power/interest grid or a RACI decision-rights matrix.