Skip to content
Skills Library
DevOps & cloud · Planning

docs-decommission

/docs-decommission

Generate DECOMMISSION-<service>.md covering infra, data, access, DNS, dependencies, monitoring, and financial checklists. Use when decommissioning a service.

Licence
MIT
Last repository change
24.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Generate DECOMMISSION-<service>.md covering infra, data, access, DNS, dependencies, monitoring, and financial checklists. Use when decommissioning a service.

Arguments

/docs-decommission <service-name>
Original author description

Generate DECOMMISSION-<service>.md covering infra, data, access, DNS, dependencies, monitoring, and financial checklists. Use when decommissioning a service.

How it works

  1. When to Use This Skill
  2. Your Task
  3. Output Format
  4. Important Notes
Original SKILL.md headings · 114 lines, 784 words
SKILL.md preview
---
created: 2025-12-16
modified: 2026-05-09
reviewed: 2026-04-25
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
- [ ] Plan for data deletion in compliance with policies
- [ ] Verify backup completion and integrity
- [ ] Document legal/compliance data retention requirements

### 4. Access and Security Checklist
- [ ] Revoke service accounts and API credentials
- [ ] Remove IAM roles and permissions
- [ ] Rotate any shared secrets or keys
- [ ] Update security groups and firewall rules
- [ ] Remove OAuth applications and integrations
- [ ] Audit and remove user access
- [ ] Update password vaults and secret managers

### 5. DNS and Networking Checklist
- [ ] Document all DNS records (A, CNAME, TXT, MX, etc.)
- [ ] Plan DNS record removal or updates
- [ ] Update load balancer configurations
- [ ] Remove or update CDN configurations
- [ ] Document any hardcoded URLs or endpoints
- [ ] Notify dependent services of endpoint changes

### 6. Integration and Dependencies Checklist
- [ ] Identify all upstream services (services this one depends on)
- [ ] Identify all downstream services (services depending on this one)
- [ ] Document API contracts and integration points
- [ ] Notify dependent teams of decommission timeline
- [ ] Plan migration path for dependent services
- [ ] Update service discovery and registries

### 7. Monitoring and Observability Cleanup
- [ ] Remove monitoring dashboards
- [ ] Delete alert rules and notification channels
- [ ] Clean up log aggregation and retention
- [ ] Remove tracing and APM configurations
- [ ] Archive historical metrics if needed
- [ ] Update status pages and documentation

### 8. Documentation and Knowledge Transfer
- [ ] Archive technical documentation
- [ ] Update architecture diagrams
- [ ] Remove or archive runbooks and SOPs
- [ ] Update team wikis and knowledge bases
- [ ] Document lessons learned
- [ ] Archive incident reports and postmortems

### 9. Financial and Administrative
- [ ] Cancel subscriptions and recurring charges
- [ ] Remove cost allocation tags
- [ ] Update budget and capacity planning
- [ ] Archive invoices and billing records
- [ ] Transfer domain registrations if needed

### 10. Final Verification
- [ ] Verify all resources are deleted or archived
- [ ] Confirm no unexpected charges appear
- [ ] Validate dependent services are functioning
- [ ] Complete decommission sign-off with stakeholders
- [ ] Archive this decommission documentation

## Output Format

Create a markdown file named `DECOMMISSION-${1:-[SERVICE_NAME]}.md` with:
- Clear section headers
- Checkboxes for each action item
- Specific resource identifiers (not generic placeholders)
- Timeline and responsible parties for each major section
- Links to relevant documentation and tools
- Emergency rollback procedures

## Important Notes

- This documentation should be created **at deployment time** when context is fresh
- Include actual resource identifiers, not examples
- Keep it updated as the service evolves
- Store it in the service repository for easy access
- Review and update quarterly or after major changes

Versions

The database has no other skills named docs-decommission.

Database snapshot: 13.11.2026 · package version bd278182544b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90decommission-sunset
    Plan the safe sunset of a service or product — deprecation policy and timeline, data retention/migration/export, user comms, contract wind-down, traffic drain, teardown, and post-sunset verification. Use when: plan to decommission the legacy billing service, sunset and deprecate…
  • 100rhdh-decommission-release
    Use when decommissioning an end-of-life RHDH release branch by removing CI config, generated Prow jobs, and branch protection from the openshift/release repository
  • 100dns-management
    Configure DNS zones and records. Manage Route53, Cloud DNS, and self-hosted DNS. Use when setting up DNS infrastructure.
  • 100decommission-plan
    Turn a system off safely - proving there are no remaining consumers, which is much harder than it sounds, then data retention and archival obligations, a staged darkening sequence, and how long to keep the ability to reverse. Use when a system is being retired, after a migration…
  • 100dns-management
    Configure DNS zones and records. Manage Route53, Cloud DNS, and self-hosted DNS. Use when setting up DNS infrastructure.
  • 80AngularJS Decommission Gate
    Decide whether AngularJS can be removed after migration work is complete. Use when hybrid dependencies, downgrade bridges, or AngularJS routes may still remain.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.