Docs Release Maintenance
Use this skill to keep developer documentation aligned with software release and maintenance lifecycles. It covers publishing readiness, ownership, automation, freshness, and responsible deprecation or deletion.
This skill is derived from Docs for Developers: An Engineer's Field Guide to Technical Writing, especially Chapter 7, "Publishing documentation," and Chapter 11, "Maintaining and deprecating documentation." It is expanded with paraphrased guidance from Christopher Gales and the Splunk Documentation Team's The Product Is Docs: Writing Technical Documentation in a Product Development Group, especially Chapter 10, "Maintaining Existing Content," Chapter 25, "Writing SaaS Documentation," and Chapter 2, "Agile." Do not copy book prose into user outputs. Source: https://link.springer.com/book/10.1007/978-1-4842-7217-6
Quick Start
- Load
guidelines.md to choose the smallest useful reference set.
- Identify the release, affected users, docs owners, source of truth, and publication path.
- Use
workflows/plan-doc-release-maintenance.md for release or maintenance planning.
- Use
workflows/refresh-existing-docs.md when stale content, patch buildup, or dependency updates require a focused refresh.
- Align doc publication, review, testing, announcement, and deprecation with code changes.
- Prefer automation that removes known toil; do not automate an unclear process.
Default Output
When planning release or maintenance work, return:
- Release or maintenance scope - code/product change and affected docs.
- User impact - who is affected and what action they need.
- Publishing checklist - owner, reviewers, approval, tests, delivery, announcement.
- Maintenance plan - owners, freshness checks, link checks, linting, generated references.
- Deprecation or deletion plan - warnings, alternatives, migration guide, redirects, and timing.
- Risks and blockers - unverified facts, missing owners, or automation gaps.
Contents
| Need |
Start Here |
| Understand release and maintenance concepts |
references/core/knowledge.md |
| Apply lifecycle rules |
references/core/knowledge.md |
| See checklist examples |
references/core/knowledge.md |
| Plan release, maintenance, or deprecation |
workflows/plan-doc-release-maintenance.md |
| Refresh existing docs |
workflows/refresh-existing-docs.md |
| Route by task |
guidelines.md |
Core Posture
- Docs should ship with the software change they explain.
- Every maintained doc needs ownership or an authoritative source.
- Automation should follow a understood manual process.
- Maintenance work should assess scope before patching content.
- Deprecation and deletion are user communication problems, not just cleanup tasks.
1---2name: docs-release-maintenance3description: Manage developer documentation release, publishing, ownership, freshness, automation, maintenance, SaaS cadence, deprecation, deletion, redirects, and migration alongside software changes. Use when planning docs for a release, defining docs ownership, creating publishing checklists, setting up freshness checks, refreshing existing content, documenting SaaS releases, or retiring stale documentation.4license: MIT5---67# Docs Release Maintenance89Use this skill to keep developer documentation aligned with software release and maintenance lifecycles. It covers publishing readiness, ownership, automation, freshness, and responsible deprecation or deletion.1011This skill is derived from *Docs for Developers: An Engineer's Field Guide to Technical Writing*, especially Chapter 7, "Publishing documentation," and Chapter 11, "Maintaining and deprecating documentation." It is expanded with paraphrased guidance from Christopher Gales and the Splunk Documentation Team's *The Product Is Docs: Writing Technical Documentation in a Product Development Group*, especially Chapter 10, "Maintaining Existing Content," Chapter 25, "Writing SaaS Documentation," and Chapter 2, "Agile." Do not copy book prose into user outputs. Source: https://link.springer.com/book/10.1007/978-1-4842-7217-61213## Quick Start14151. Load `guidelines.md` to choose the smallest useful reference set.162. Identify the release, affected users, docs owners, source of truth, and publication path.173. Use `workflows/plan-doc-release-maintenance.md` for release or maintenance planning.184. Use `workflows/refresh-existing-docs.md` when stale content, patch buildup, or dependency updates require a focused refresh.195. Align doc publication, review, testing, announcement, and deprecation with code changes.206. Prefer automation that removes known toil; do not automate an unclear process.2122## Default Output2324When planning release or maintenance work, return:25261. **Release or maintenance scope** - code/product change and affected docs.272. **User impact** - who is affected and what action they need.283. **Publishing checklist** - owner, reviewers, approval, tests, delivery, announcement.294. **Maintenance plan** - owners, freshness checks, link checks, linting, generated references.305. **Deprecation or deletion plan** - warnings, alternatives, migration guide, redirects, and timing.316. **Risks and blockers** - unverified facts, missing owners, or automation gaps.3233## Contents3435| Need | Start Here |36|------|------------|37| Understand release and maintenance concepts | `references/core/knowledge.md` |38| Apply lifecycle rules | `references/core/knowledge.md` |39| See checklist examples | `references/core/knowledge.md` |40| Plan release, maintenance, or deprecation | `workflows/plan-doc-release-maintenance.md` |41| Refresh existing docs | `workflows/refresh-existing-docs.md` |42| Route by task | `guidelines.md` |4344## Core Posture4546- Docs should ship with the software change they explain.47- Every maintained doc needs ownership or an authoritative source.48- Automation should follow a understood manual process.49- Maintenance work should assess scope before patching content.50- Deprecation and deletion are user communication problems, not just cleanup tasks.
LVTD-LLC