Context7
compozy/compozy
Retrieves authoritative, up-to-date technical documentation, API references, configuration details, and code examples for any developer technology.
Plan the communications for deprecating a product, API, endpoint, or feature that customers depend on.
Install Deprecation Comms Plan
$ npx skills add mohitagw15856/pm-claude-skills --skill deprecation-comms-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills deprecation-comms-plan --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/deprecation-comms-plan .claude/skills/deprecation-comms-plan && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "deprecation-comms-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/deprecation-comms-plan into .claude/skills/deprecation-comms-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deprecation-comms-plan", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/deprecation-comms-planType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill deprecation-comms-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills deprecation-comms-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/deprecation-comms-plan .agents/skills/deprecation-comms-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deprecation-comms-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/deprecation-comms-plan into .agents/skills/deprecation-comms-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deprecation-comms-plan", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill deprecation-comms-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills deprecation-comms-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/deprecation-comms-plan .cursor/skills/deprecation-comms-plan && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "deprecation-comms-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/deprecation-comms-plan into .cursor/skills/deprecation-comms-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deprecation-comms-plan", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/deprecation-comms-plan--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill deprecation-comms-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills deprecation-comms-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/deprecation-comms-plan .gemini/skills/deprecation-comms-plan && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "deprecation-comms-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/deprecation-comms-plan into .gemini/skills/deprecation-comms-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deprecation-comms-plan", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills deprecation-comms-planInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill deprecation-comms-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/deprecation-comms-plan .github/skills/deprecation-comms-plan && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "deprecation-comms-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/deprecation-comms-plan into .github/skills/deprecation-comms-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deprecation-comms-plan", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill deprecation-comms-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills deprecation-comms-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/deprecation-comms-plan .opencode/skills/deprecation-comms-plan && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "deprecation-comms-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/deprecation-comms-plan into .opencode/skills/deprecation-comms-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deprecation-comms-plan", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
deprecation-comms-plan- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 532 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plan the communications for deprecating a product, API, endpoint, or feature that customers depend on.
- Sunsetting something
- SKILL.md covers Working from a brief, Required Inputs, Output Format and Quality Checks, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Planning a breaking change
What it does
Deprecation Comms Plan is an agent skill from mohitagw15856/pm-claude-skills. 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…
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Code migrations and REST APIs. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Sunsetting something
- Planning a breaking change
- Migrating customers off a legacy path
Example prompts
- “/deprecation-comms-plan”
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Deprecation Comms Plan loads about 1.1k tokens when it runs. Until then it costs about 159 tokens; SKILL.md has 532 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 532 words, ~1,096 tokens.
Download SKILL.mdSave it as
.claude/skills/deprecation-comms-plan/SKILL.md (or your agent's skills folder).- name
- deprecation-comms-plan
- description
- 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).
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 principle you're committing to (e.g. "announce → N months deprecated (works, warns) → sunset, with a migration path live before we announce").
Timeline
| Phase | Date / window | What changes | What customers can still do |
|---|---|---|---|
| Announce | nothing breaks; docs + warnings | full use, start migrating | |
| Deprecated | warnings, no new adoption | migrate | |
| Sunset | turned off | must have migrated |
Include grace periods and any extension policy for large accounts.
Tiered messaging
Segmented by dependence, not one blast:
- Tier 1 — heavy/contractual users: proactive, human (CSM/AM), often a call + tailored plan.
- Tier 2 — active users: direct email + in-product warning + migration guide.
- Tier 3 — light/dormant: changelog, docs banner, deprecation headers.
For each: the core message (what, when, why, what to do), the ask, and the escalation path.
Migration guide outline
The structure of the how-to: before/after, step-by-step, code/config examples, a mapping table (old → new), FAQ, and where to get help.
Show full SKILL.md (206 more words)Show less
Channel plan
Which channels fire at which phase — email, in-product, docs/changelog, API deprecation headers/Sunset header, status page, community/social — and the cadence (announce, reminders at intervals, final notice).
Internal escalation playbook
The at-risk account list, who owns each, the CSM talking points, the "customer can't migrate in time" decision tree, and the exception/extension approval path.
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
- 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
Anti-Patterns
- 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
- "Why" that blames the customer or the old system instead of owning the change
Example Trigger Phrases
- "Winding down."
- "Plan a breaking change."
- "Migrate customers off a legacy path."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/deprecation-comms-plan of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Deprecation Comms Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Deprecation Comms Plan this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Context7compozy/compozy | 2.8k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Store Submitzhitongblog/solomd | 1.2k | — | ~1.7k | Automated safety check: Notes | MIT | |
| Migration PathAxonIQ/AxonFramework | 3.6k | — | ~594 | Automated safety check: Pass | Apache-2.0 | |
| Groovy 5 Developer Guideapache/grails-core | 2.9k | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Saleor Port Changessaleor/saleor | 23k | — | ~969 | Automated safety check: Pass | BSD-3-Clause |
Similar skills
Store Submit
zhitongblog/solomd
Publish a SoloMD release to the stores that have no usable submission API — Google Play Console and Microsoft Partner Center — by driving them through the local Unzoo Browser REST API.
Migration Path
AxonIQ/AxonFramework
Create a new Axon Framework 4→5 migration path documentation page.
Groovy 5 Developer Guide
apache/grails-core
Guidance for Groovy 5 work in Grails projects: syntax, closures, traits, DSLs, metaprogramming, Spock tests, static compilation and Java 21 integration.
Saleor Port Changes
saleor/saleor
Forward-ports or backports a single PR or branch onto the currently checked-out Saleor branch, handling GraphQL version markers and migration numbering along the way.
Breaking Change Analysis
ruby-git/ruby-git
Assesses what an API change would break before it is made, finds every usage, documents the impact and plans a deprecation or migration path.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Deprecation Comms Plan
What does Deprecation Comms Plan do?
Plan the communications for deprecating a product, API, endpoint, or feature that customers depend on. Deprecation Comms Plan is an agent skill from mohitagw15856/pm-claude-skills. Plan the communications for deprecating a product, API, endpoint, or feature that customers depend on.
When should I use Deprecation Comms Plan?
Deprecation Comms Plan fits situations like: sunsetting something; planning a breaking change; migrating customers off a legacy path.
How do I install Deprecation Comms Plan in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill deprecation-comms-plan -a claude-code`. Or copy the skill folder (skills/deprecation-comms-plan in mohitagw15856/pm-claude-skills) into .claude/skills/deprecation-comms-plan in your project. Claude Code loads it when a task matches its description.
How do I install Deprecation Comms Plan in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill deprecation-comms-plan -a codex`. Or copy the skill folder (skills/deprecation-comms-plan in mohitagw15856/pm-claude-skills) into .agents/skills/deprecation-comms-plan in your project. Codex loads it when a task matches its description.
Can I use Deprecation Comms Plan in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill deprecation-comms-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deprecation-comms-plan, .gemini/skills/deprecation-comms-plan, .github/skills/deprecation-comms-plan and .opencode/skills/deprecation-comms-plan in your project.
What does Deprecation Comms Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Deprecation Comms Plan is instructions for the agent only.
Does Deprecation Comms Plan access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Deprecation Comms Plan safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Deprecation Comms Plan use?
Deprecation Comms Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Deprecation Comms Plan use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Deprecation Comms Plan?
Skills that share tags, products or a category with Deprecation Comms Plan: Context7 (compozy/compozy, 2.8k stars), Store Submit (zhitongblog/solomd, 1.2k stars), Migration Path (AxonIQ/AxonFramework, 3.6k stars) and Groovy 5 Developer Guide (apache/grails-core, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Deprecation Comms Plan?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.