From docops
Docops: mark documentation for deprecation with configurable grace period before archival. Adds deprecation banner, updates references, schedules archive date. Use when: 'deprecate this doc', 'mark for removal'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/docops:deprecateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Mark documentation for deprecation with grace period before archival.
Mark documentation for deprecation with grace period before archival.
context_preflight mandatory before execution (flow='generic').--days N. Grace periods: SPEC 30d, REF 30d, HOWTO 14d, RUNBOOK 7d, ADR never.context_record_outcome after execution.context_preflight with flow='generic'; block execution if preflight fails.--days N).> [!WARNING] deprecation banner at top of file.status: deprecated, deprecated_on, deprecated_by, deprecation_reason, archive_on, replacement.archive_on: today + grace period (minimum 7 days).[DEPRECATED] marker next to links pointing to this file.context_record_outcome.> [!WARNING] at top[DEPRECATED]npx claudepluginhub murillodutt/cellm --plugin docopsPlans and executes removal of deprecated APIs without breaking consumers. Includes pre-removal checklist, blast radius decomposition, and step-by-step migration process.
Plans and executes deprecation lifecycle for design system components, tokens, patterns: audits usage via grep, sets timelines, migration paths, communication plans, multi-phase removal.
Manages deprecation and migration of old systems, APIs, or features. Guides removal of legacy code, sunsetting features, consolidating duplicates, and lifecycle planning.