eol-checklist — Claude Code skill: what it does, how to install
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.
npx skills add deanpeters/Product-Manager-Skills --skill eol-checklist -a claude-codeWhat eol-checklist does
The skill converts a completed sunset decision into an operational execution plan. Each checklist entry spans four to eight words, opens with a verb, and tags a department rather than an individual calendar. That functional ownership quickly exposes gaps across teams before dates slip.
Scope matches the retirement risk across three distinct levels. Level 2 serves as the default, covering eleven functional areas across major lifecycle milestones from announcement to final shutdown. A minor internal script receives a brief punch list, while heavily regulated hardware runs through all fifteen areas with strict sign-offs between gates.
This is not a project management scheduler. You will not find Gantt charts or task dependency trees here. The prompt assumes the retirement decision is settled, so it turns your timelines and constraints into clear commitments instead of speculative debates.
What it helps with
- build an operational retirement plan for a commercial service
- assign functional ownership across departments during a deprecation
- set gate approval criteria before pulling the plug on a product
- manage shutdown steps for hardware lines with partner contracts
Example prompts for the agent
- Generate an EOL checklist for our legacy analytics module closing Dec 31 with 400 customer accounts.
- Create a heavy sunset checklist for hardware with service contracts and eight resellers.
- Build a light deprecation punch list for an unversioned internal API.
How to install eol-checklist
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-checklist -a claude-code2Manually: put the files in place
~/.claude/skills/eol-checklist/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/eol-checklist/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-checklist -a codex2Manually: put the files in place
.agents/skills/eol-checklist/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-checklist -a cursor2Manually: put the files in place
.cursor/skills/eol-checklist/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install deanpeters/Product-Manager-Skills eol-checklist2Manually: put the files in place
.github/skills/eol-checklist/SKILL.md1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-checklist -a gemini-cli2Platform CLI
gemini skills install https://github.com/deanpeters/Product-Manager-Skills --path skills/eol-checklistManually: put the files in place
.devin/skills/eol-checklist/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill eol-checklist -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-checklist
How do I install eol-checklist in Claude Code?
Run npx skills add deanpeters/Product-Manager-Skills --skill eol-checklist -a claude-code in your terminal. This registers the skill with your Claude Code agent.
What does eol-checklist do?
It generates a phase-gated retirement plan with brief action items assigned to functional roles like legal, sales, or engineering.
What information does the skill need to start?
It works best with the product name and target shutdown dates. If you provide no details upfront, it asks up to three clarifying questions before drafting the list.