FS
Feature Sunset Plan
🔵 Stable 🕐 updated 2026-07-02
🔷 SkillSpec L3
pm-planning
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.
What to give it
▸ 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 nothing
▸ Constraints — renewal cycles to respect, compliance data-retention duties, support capacity for the transition
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓ The decision record includes sunset success criteria, not just kill reasons
✓ Users are segmented by depth; dependent accounts are contacted before any public notice
✓ Every migration path states what's lost, not just what's equivalent
✓ Contractual and compliance checks are documented, not assumed
✓ The timeline ends in *deleted code*, with an owner for the deletion
✓ The exception policy has a maximum — extensions are bounded by design
⚠️ What it refuses to do
Do not announce by blog post before dependent customers hear it from their account team
Do not use raw usage percentage as the whole case — depth and contracts decide who can veto your math
Do not promise the replacement is equivalent when it isn't — name the losses; users find them anyway
Do not grant open-ended exceptions — one immortal customer instance is the whole maintenance cost with none of the revenue
Do not declare victory at shutoff — the sunset is done when the code is gone and the retro is filed
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcpStart with
Related skills
🔌 Embed this skill
Drop this on your blog, docs, or site — it renders a "Run this skill" card:
<div data-pm-skill="feature-sunset-plan"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>💬 Discussion