Skip to main content
skill CX Codex

eol-stakeholder-sequence — Claude Code skill: how to install

This skill organizes stakeholder meetings before retiring a product. It uncovers contractual and operational pitfalls prior to any public announcement.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence -a claude-code
Open on GitHub

What eol-stakeholder-sequence does

The skill structures internal conversations when an end-of-life decision is made. Discussions start with legal and finance teams, then proceed to sales, marketing, and customer support. Talking to departments that can halt the shutdown takes priority over notifying technical teams.

Level 2 serves as the default option with seven or eight stops. Level 3 is heavier. It targets hardware lines and regulated products where oversight runs strict. Skipping legal review on contracted offerings breaks the retirement plan early.

Each stop defines what information to gather, what context to provide, and which red flags to monitor. If you do not supply product details upfront, the assistant asks up to three clarifying questions before producing short bullet points.

What it helps with

  • sequence internal stakeholder reviews before sunsetting a product
  • surface contractual liabilities before informing customers
  • track undocumented promises made by sales representatives
  • define inputs and commitments needed for each department meeting

Example prompts for the agent

  • Plan the stakeholder conversation order for deprecating our legacy reporting system.
  • Map out who to interview first when sunsetting a commercial hardware line.
  • Create a sequence of internal review stops for retiring an outdated API module.

How to install eol-stakeholder-sequence

1Skills CLI (Vercel)

npx skills add deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence -a claude-code

2Manually: put the files in place

~/.claude/skills/eol-stakeholder-sequence/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/eol-stakeholder-sequence/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about eol-stakeholder-sequence

How to install eol-stakeholder-sequence in Claude Code?

Run npx skills add deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence -a claude-code in your terminal.

What does eol-stakeholder-sequence do?

It generates an ordered itinerary of stakeholder conversations when sunsetting a feature or product. This helps discover hidden liabilities before making external announcements.

Why should legal be consulted before engineering?

Unchecked contract terms can halt deprecation after teams have already spent effort on execution. Legal review confirms whether contractual obligations permit the sunset.

Similar skills

Everything for Notes, tasks and projects →

From the same set69

intelligence-collection-disciplines A skill that splits market and competitor research into eight collection channels, then fuses the results. Three weak but independent signals beat one loud claim. CX Codex +1 1,100installs competitive-intel-watch Diffs competitor activity against a prior research snapshot and logs only actionable shifts. Flags outdated battle cards and pricing notes without regenerating full reports. CX Codex +1 1,100installs eol-checklist Creates a phase-gated product sunset checklist tailored to project scale. It assigns actionable tasks with functional owners so retirements finish without stranded data or contracts. CX Codex +1 913installs eol-process Guides product sunset workflows across every phase, from initial decisions to post-mortem reviews. It helps retire software while keeping customer trust. CX Codex +1 909installs eol-readiness-advisor This skill assesses whether a product or feature should reach end of life and sizes the transition work. Use it when the retirement decision is stuck. CX Codex +1 905installs pestel-delta-monitor Diffs macro market shifts against a baseline PESTEL assessment to spot invalid assumptions. CX Codex +1 902installs porters-five-forces Evaluates market structure through Porter's forces and verified signals to test expansion bets or explain falling margins. CX Codex +1 885installs stakeholder-mapping Maps stakeholders across two 2x2 grids to balance executive priorities against the needs of impacted users who lack organizational authority. CX Codex +1 868installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor