deprecate-component

Automate deprecation of framework components with timelines and migration guides.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/GDSDN/kord-aios --skill deprecate-component
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deprecate-component
Source: https://github.com/GDSDN/kord-aios/tree/main/src/features/builtin-skills/kord-aios/dev-workflow/deprecate-component
Command: npx skills add https://github.com/GDSDN/kord-aios --skill deprecate-component

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of marking framework components (agents, tasks, workflows, utilities) as deprecated, ensuring a smooth transition for users and maintaining codebase health.

Core Features & Use Cases

  • Automated Deprecation: Marks components as deprecated with configurable timelines and reasons.
  • Migration Path Generation: Creates migration guides and suggests replacements.
  • Impact Analysis: Identifies components and usage sites affected by deprecation.
  • Use Case: When a specific agent is found to be inefficient or superseded by a new one, this Skill can be used to formally deprecate it, notify users, and provide instructions on how to switch to the new agent.

Quick Start

Deprecate the 'old-logger' utility, setting a 6-month timeline and specifying '@kord-aios/logger' as the replacement.

Frequently Asked Questions about deprecate-component

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deprecate framework components safely without breaking existing workflows?

Deprecating framework components safely requires automating the deprecation timeline, generating migration guides, and analyzing component usage to identify affected areas. This ensures a structured transition without breaking existing workflows.

What is the best way to generate a migration guide when replacing an old agent?

Generating a migration guide is handled by automated deprecation, which marks the old agent as deprecated and suggests specific replacements. This formalizes the transition and provides clear instructions for users to switch components.

Can I set a specific deprecation timeline for utilities in a codebase?

Yes, you can configure a specific deprecation timeline for utilities. The automated deprecation process supports configurable timelines, allowing you to define exact schedules and state reasons for phasing out codebase components.

How does impact analysis work when deprecating tasks and workflows?

Impact analysis for deprecating tasks and workflows works by examining the codebase to identify usage sites and dependent components affected by the deprecation. This maps all affected areas before the component is retired.

When should I automate component lifecycle management for framework maintenance?

You should automate component lifecycle management when a framework component is superseded or found to be inefficient. This ensures formal deprecation, user notification, and structured migration instructions for framework maintenance.

Are there limitations to using automated deprecation for codebase management?

Automated deprecation for codebase management is limited by its dependency on explicit replacement definitions. It analyzes usage and generates timelines, but you must manually specify the correct replacement component to ensure a valid migration path.