deprecation-manager

Manage API and SDK deprecation lifecycle

509 stars

Best use case

deprecation-manager is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Manage API and SDK deprecation lifecycle

Teams using deprecation-manager should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/deprecation-manager/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/library/specializations/sdk-platform-development/skills/deprecation-manager/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/deprecation-manager/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How deprecation-manager Compares

Feature / Agent	deprecation-manager	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Manage API and SDK deprecation lifecycle

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Deprecation Manager Skill

## Overview

This skill manages the complete deprecation lifecycle for APIs and SDKs, from initial deprecation notices through sunset, ensuring smooth transitions for API consumers.

## Capabilities

- Track deprecation timelines and milestones
- Inject deprecation warnings in SDK code
- Send sunset notifications to API consumers
- Generate migration documentation automatically
- Monitor deprecated endpoint usage
- Configure Sunset and Deprecation HTTP headers
- Implement gradual deprecation with usage thresholds
- Archive deprecated documentation appropriately

## Target Processes

- Backward Compatibility Management
- API Versioning Strategy
- SDK Versioning and Release Management

## Integration Points

- Sunset header injection middleware
- Deprecation annotation processors
- Usage analytics systems
- Email/notification services
- Documentation platforms

## Input Requirements

- Deprecation policy and timelines
- Affected endpoints/features list
- Replacement/migration paths
- Consumer notification requirements
- Usage monitoring access

## Output Artifacts

- Deprecation timeline documentation
- SDK deprecation annotations
- Migration guides
- Sunset header configurations
- Consumer notification templates
- Usage monitoring dashboards
- Archived documentation

## Usage Example

```yaml
skill:
  name: deprecation-manager
  context:
    deprecationPolicy: ./docs/deprecation-policy.md
    features:
      - featureId: legacy-auth
        deprecationDate: "2024-06-01"
        sunsetDate: "2024-12-01"
        replacement: oauth2-flow
    notificationChannels:
      - email
      - dashboard
      - sdkWarnings
    usageThreshold: 100
```

## Best Practices

1. Announce deprecations well in advance (6+ months)
2. Provide clear migration paths with examples
3. Monitor usage before sunset
4. Send multiple reminder notifications
5. Keep deprecated docs available but marked
6. Implement gradual rate limiting before full sunset