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.
npx skills add deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence -a claude-codeWhat 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-code2Manually: put the files in place
~/.claude/skills/eol-stakeholder-sequence/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/eol-stakeholder-sequence/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence -a codex2Manually: put the files in place
.agents/skills/eol-stakeholder-sequence/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence -a cursor2Manually: put the files in place
.cursor/skills/eol-stakeholder-sequence/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install deanpeters/Product-Manager-Skills eol-stakeholder-sequence2Manually: put the files in place
.github/skills/eol-stakeholder-sequence/SKILL.md1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence -a gemini-cli2Platform CLI
gemini skills install https://github.com/deanpeters/Product-Manager-Skills --path skills/eol-stakeholder-sequenceManually: put the files in place
.devin/skills/eol-stakeholder-sequence/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-stakeholder-sequence -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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.