Overview

This is a deprecated wrapper kept for backward compatibility. The recommended path is to migrate to the focused extension skills (umbrella routing, hooks, agent-skills, sub-agents, teams, and plugin). For cross-component validation, rely on plugin-verification.

How This Skill Works

The skill no longer adds new functionality and serves as a compatibility layer pointing to newer focused SKILLs. It exists to ease migration by preserving references while teams transition to dedicated extension skills.

When to Use It

• Maintaining an existing deployment that still references plugin-implementation-deprecated.
• Auditing skill usage to map old references to new focused extension skills during migration.
• Running compatibility checks with plugin-verification across components during a transition.
• Documenting deprecated references as part of a migration plan.
• Planning a phased migration to implement-claude-extensions, implement-hooks, implement-agent-skills, implement-sub-agents, implement-agent-teams, or implement-plugin.

Quick Start

1. Step 1: Identify all references to plugin-implementation-deprecated in configs, docs, and automation.
2. Step 2: Map each reference to the appropriate focused skill (umbrella routing, hooks, etc.).
3. Step 3: Run plugin-verification to validate integration and remove the deprecated skill from active deployments.

Best Practices

• Do not add new logic to this deprecated skill; migrate to the focused SKILLs instead.
• Document every reference to the deprecated skill for traceability.
• Use plugin-verification to validate integration as you migrate components.
• Replace umbrella routing, hooks, and other functions with their dedicated SKILL counterparts.
• Prioritize migrating critical workflows first and retire the deprecated entry once migrated.

Example Use Cases

• A legacy deployment still routes through plugin-implementation-deprecated, which forwards to implement-claude-extensions for umbrella routing.
• An automation script maps old plugin-implementation-deprecated calls to implement-hooks during a migration sprint.
• QA runs plugin-verification to ensure compatibility while transitioning to the focused extension skills.
• An org audits skill references and creates a plan to replace plugin-implementation-deprecated with implement-agent-skills or implement-sub-agents as appropriate.
• Team schedules a phased migration timeline, documenting deprecated references and the cutover to new focused SKILLs.

Frequently Asked Questions