What do I need to use Deprecation Comms Plan?

What's being deprecated; Who depends on it; The replacement / migration path; Hard constraints.

Is Deprecation Comms Plan free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Deprecation Comms Plan

Q: How do I know the Deprecation Comms Plan output is good?

The skill verifies itself against its own quality checks: A migration path exists and is referenced everywhere before any customer message goes out; Runway is sized to migration difficulty, with grace periods stated; Messaging is tiered by dependence; Tier-1 accounts get a human, not a blast; Every message says what, when, why, and the exact next step.

🔵 Stable🕐 updated 2026-07-23 🔷 SkillSpec L3 pm-devrel

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 mechanics).

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸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

✅ 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.

✓A migration path exists and is referenced everywhere before any customer message goes out

✓Runway is sized to migration difficulty, with grace periods stated

✓Messaging is tiered by dependence; Tier-1 accounts get a human, not a blast

✓Every message says what, when, why, and the exact next step

✓The channel cadence includes reminders and a final notice, not a single announcement

✓High-risk accounts have a named owner and an escalation/extension path

⚠️ What it refuses to do

Too little runway for the migration actually required

A silent breaking change, or burying it in a changelog nobody reads

Announcing before the migration path is live

One-size messaging that treats a whale like a dormant free user

No plan for the accounts that physically can't migrate in time

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-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="deprecation-comms-plan"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Deprecation Comms Plan is one of 832 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog