docs-decommission

created	"2025-12-16T00:00:00.000Z"
modified	"2026-05-09T00:00:00.000Z"
reviewed	"2026-04-25T00:00:00.000Z"
allowed-tools	Read, Write, Edit, Bash(find *), Bash(ls *), Grep, TodoWrite
args	<service-name>
argument-hint	<service-name>
disable-model-invocation	true
description	Generate DECOMMISSION-<service>.md covering infra, data, access, DNS, dependencies, monitoring, and financial checklists. Use when decommissioning a service.
name	docs-decommission

Service Decommission Documentation Generator

When to Use This Skill

Use this skill when...	Use docs-generate instead when...
Retiring or shutting down a deployed service and need a complete teardown checklist	Producing API reference, README, or CHANGELOG content from code annotations
Capturing infrastructure, DNS, secrets, and billing cleanup steps at deployment time while context is fresh	Drafting general project documentation that will be maintained alongside development
Generating a service-specific DECOMMISSION-<service>.md with environments, stakeholders, and rollback steps	Synchronising existing documentation with the current codebase (use docs-sync)

Generate a comprehensive decommission checklist for ${1:-[SERVICE_NAME]} to be created at deployment time when all context is fresh.

Your Task

Create a detailed decommission documentation file that includes:

1. Service Overview

• Document the service name, purpose, and deployment date
• List all environments (dev, staging, production)
• Note key stakeholders and team contacts
• Record repository and deployment locations

2. Infrastructure Resources Checklist

Create a checklist covering:

• Cloud resources (compute instances, containers, serverless functions)
• Storage resources (databases, object storage, file systems, volumes)
• Network resources (load balancers, DNS records, CDN configurations)
• Security resources (SSL certificates, API keys, service accounts, IAM roles)
• Monitoring and alerting (dashboards, alert rules, log aggregations)
• CI/CD pipelines and automation jobs
• Scheduled tasks and cron jobs

3. Data Management Checklist

• Identify all data stores and their locations
• Create data backup procedures and retention policies
• Document data migration or archival requirements