deprecation-comms-plan
Plan the communications for deprecating a product, API, endpoint, or feature that customers depend on. Use when winding down or sunsetting something, planning a breaking change, or migrating customers off a legacy path. Produces a staged timeline with grace periods, tiered customer messaging, a migration-guide outline, the channel plan, and an internal escalation playbook for the highest-risk accounts. This is the customer-communications program — distinct from [[feature-sunset-plan]] (the kill decision, data handling, and code removal) and [[api-versioning-strategy]] (the technical versioning
npx skills add mohitagw15856/pm-claude-skills --skill deprecation-comms-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.
# Deprecation Comms Plan Skill Deprecations go wrong in two ways: too fast (customers get broken and churn angry) or too quiet (they find out when it breaks). This skill plans the wind-down as a *communications program*, not an announcement — enough runway, messaging matched to how much each customer depends on the thing, a real migration path, and a plan for the accounts that will need a human. ## Working from a brief Given what's being deprecated and why, **produce the full plan** — infer the risk tiers from usage and contract exposure. Right-size the runway to how hard the migration is (an internal flag flip is weeks; a public API is many months). If there's no migration path yet, flag that as a blocker before any announcement. ## Required Inputs Ask for (if not provided, else infer and label the assumption): - **What's being deprecated** and **why** (cost, security, strategy, replaced-by) - **Who depends on it** — rough usage, and which segments/contracts are exposed - **The replacement / migration path** (or that there isn't one yet) - **Hard constraints** — a forcing date (security, legal, contract), team capacity ## Output Format ### Deprecation policy in one line The princi
- Working from a brief
- Required Inputs
- Output Format
- Deprecation policy in one line
- Timeline
- Tiered messaging
- Migration guide outline
- Channel plan
- Internal escalation playbook
- Quality Checks
- Anti-Patterns
What does the deprecation-comms-plan skill do?
Plan the communications for deprecating a product, API, endpoint, or feature that customers depend on. Use when winding down or sunsetting something, planning a breaking change, or migrating customers off a legacy path. Produces a staged timeline with grace periods, tiered customer messaging, a migration-guide outline, the channel plan, and an internal escalation playbook for the highest-risk accounts. This is the customer-communications program — distinct from [[feature-sunset-plan]] (the kill decision, data handling, and code removal) and [[api-versioning-strategy]] (the technical versioning
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill deprecation-comms-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.