eol-checklist
Build a phase-gated EOL checklist sized to the sunset, with a named owner on every item. Use when the decision to retire is made and you need the operational plan.
Profile →npx skills add deanpeters/Product-Manager-Skills --skill eol-checklist --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 Checklist ## Purpose Turn a sunset decision into a phase-gated operational plan: what must happen, in which lifecycle phase, and who owns it. The output is a working checklist — sticky-note-sized items, each with a verb and a named function — not a strategy document. The checklist is **sized to the sunset**. A deprecated internal tool gets a dozen items across three phases. A regulated hardware line gets a cross-functional playbook across six phases with gate criteria between them. Both are correct; using the wrong one is the failure. ## Input **Works best with:** The product being sunset and any dates you're already committed to. **Also useful:** Customer and revenue scale, whether a replacement exists and how ready it is, contract or regulatory obligations, and whether hardware, inventory, or channel partners are in play. 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 at what scale, whether there's a repl
- Purpose
- Input
- Key Concepts
- Right-Size Before You Build
- The Lifecycle Gates
- The Fifteen Functional Areas
- The Sticky-Note Rule
- Phase Gates Are Commitments, Not Dates
- Anti-Patterns (what this is NOT)
- Application
- Step 1: Set the level
- Step 2: Select phases in scope
- Step 3: Build items per phase, per area
- Step 4: Write gate criteria (Level 2+)
What does the eol-checklist skill do?
Build a phase-gated EOL checklist sized to the sunset, with a named owner on every item. Use when the decision to retire is made and you need the operational plan.
How do I install it?
Run `npx skills add deanpeters/Product-Manager-Skills --skill eol-checklist --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.