mcpField
F
feature-sunset-deprecation-review

feature-sunset-deprecation-review

github.com/sylphxaiDevelopment144 installsUpdated today
Repository

About feature-sunset-deprecation-review

A skill for product and engineering teams planning a feature sunset or deprecation. It structures usage evidence, migration paths, customer communication, support readiness, and rollback criteria into an actionable plan.

Key features

  1. 01Sunset scope and dependency mapping
  2. 02Usage thresholds and notice planning
  3. 03Migration and exception planning
  4. 04Support and customer communication checklists
  5. 05Rollback and cleanup criteria

Use cases

  1. 01Retiring an API version
  2. 02Sunsetting a product feature
  3. 03Planning an integration shutdown
  4. 04Preparing customer migration and support

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill feature-sunset-deprecation-review

After installing, type/feature-sunset-deprecation-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/feature-sunset-deprecation-patterns.md

Details

From the project README

Feature Sunset Deprecation Review

Use this skill to convert a feature sunset, deprecation, migration alternatives, customer communication, support readiness, and cleanup question into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify feature owner, dependency map, active usage, customer segments, contractual commitments, replacement path, and shutdown reason.
  2. Read references/feature-sunset-deprecation-patterns.md.
  3. Classify sunset type: UI feature, API version, pricing plan, integration, platform support, data format, workflow, or time-limited game/live feature.
  4. Define usage thresholds, notice timeline, migration tooling, exceptions, support playbook, kill switch, and cleanup verification.
  5. Produce deprecation plan, state machine, customer decision table, event schema, comms checklist, and rollback/extension criteria.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not remove a used capability without usage readback, impacted account list, migration path, and support owner.
  • Do not rely on one generic changelog entry for high-impact or contract-bound customers.
  • Do not keep deprecated features alive indefinitely without explicit owner, cost, risk, and exception expiry.
  • Do not delete customer data, integrations, exports, or audit evidence before retention and legal obligations are checked.

Output format

Sunset context:
Capability / users impacted / commitments:

Deprecation plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Migration and communication:
- <item> -> <policy, metric, edge case, support note>

Extension and cleanup criteria:
- <trigger> -> <action, communication, owner>

Comments

Markdown supported