feature-sunset-plan
Plan the retirement of a product feature — the kill decision made honest, user migration, data handling, comms sequencing, and the code actually deleted. Use when deprecating or sunsetting a feature, killing an underused capability, retiring an AI feature that didn't land, or when a 'deprecated' feature has haunted the codebase for two years. Produces a sunset plan: the decision record, affected-user analysis, migration paths, a staged timeline with comms per stage, and the removal checklist. For API deprecation specifically use api-versioning-strategy.
npx skills add mohitagw15856/pm-claude-skills --skill feature-sunset-plan --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.
# Feature Sunset Plan Skill Products are good at shipping and terrible at unshipping: features limp on for years because nobody owns the removal, and when a kill finally happens it's announced badly, migrates nobody, and leaves the code behind anyway. A sunset is a *product launch in reverse* — it deserves the same rigour. This skill plans the whole arc, decision to deletion. ## What This Skill Produces - A **decision record**: why this feature dies, the evidence, and what was considered instead - An **affected-user analysis** — who actually uses it, how deeply, and who screams - **Migration paths** per user segment, with the no-path-exists cases faced honestly - A **staged timeline** with comms per stage, and the **removal checklist** that ends in deleted code ## Required Inputs Ask for (if not already provided): - **The feature and the evidence for killing it**: usage data (who/how many/how deeply — depth matters more than counts), cost to maintain, what it blocks - **The user reality**: any contractual commitments, enterprise customers with it in their workflow, data users have stored in it - **What replaces it** — an internal alternative, a competitor hand-off, or honestly noth
- What This Skill Produces
- Required Inputs
- Sunset Method
- Output Format
- Sunset Plan: [feature] — target removal [date]
- Quality Checks
- Anti-Patterns
What does the feature-sunset-plan skill do?
Plan the retirement of a product feature — the kill decision made honest, user migration, data handling, comms sequencing, and the code actually deleted. Use when deprecating or sunsetting a feature, killing an underused capability, retiring an AI feature that didn't land, or when a 'deprecated' feature has haunted the codebase for two years. Produces a sunset plan: the decision record, affected-user analysis, migration paths, a staged timeline with comms per stage, and the removal checklist. For API deprecation specifically use api-versioning-strategy.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill feature-sunset-plan --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 mohitagw15856/pm-claude-skills, a repository with 1,255 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.