documentation-maintainer

name	documentation-maintainer
description	Describe what this skill helps an agent do.
version	0.1.0
since	2026-07-28
last_modified	2026-07-28
authors	["platform-engineering"]
stability	experimental
min_platform_version	{"codex":"unknown","amazon-q":"unknown","antigravity":"unknown","auggie":"unknown","bob":"unknown","claude-code":"unknown","cline":"unknown","codebuddy":"unknown","continue":"unknown","costrict":"unknown","crush":"unknown","github-copilot":"unknown","gitlab-duo":"unknown","factory":"unknown","forgecode":"unknown","opencode":"unknown","openhands":"unknown","cursor":"unknown","roo-code":"unknown","kiro":"unknown","junie":"unknown","gemini-cli":"unknown","iflow":"unknown","kilocode":"unknown","kimi":"unknown","lingma":"unknown","pi":"unknown","qoder":"unknown","qwen":"unknown","windsurf":"unknown","ollama":"unknown"}
deprecated_since	null
replaces	null
supersedes	[]
changelog	[{"version":"0.1.0","date":"2026-07-28","change":"Initial generated production-ready SDLC / DevSecOps skill"}]

Documentation Maintainer

Purpose

Keep technical and operational documentation accurate and useful across README, architecture docs, runbooks, API docs, changelogs, setup instructions, configuration docs, examples, troubleshooting, ownership, freshness, and consistency.

When to use

• A code, configuration, API, CLI, deployment, or workflow change requires documentation updates.
• README files, ADRs, runbooks, setup guides, API docs, examples, or changelogs may be stale.
• Users or operators need accurate install, upgrade, rollback, troubleshooting, or support instructions.
• Generated docs or platform-specific copies must stay aligned with canonical documentation.
• The central agent routes documentation freshness, completeness, or consistency work to this skill.

Operating model

1. Identify the changed behavior, interface, setup step, operational procedure, or decision that documentation must describe.
2. Map the change to concrete documentation artifacts: README, ADR, runbook, API reference, setup guide, example, changelog, or release note.
3. Compare documentation claims against repository evidence such as commands, flags, config keys, API schemas, workflow files, and generated outputs.
4. Classify stale, missing, contradictory, or unsafe documentation by user impact and operational risk.
5. Recommend exact documentation edits, owners, and validation commands instead of broad documentation advice.

Spec-Driven Change Context

• Treat repository specs, ADRs, runbooks, change proposals, design notes, and task files as durable context that outlives a chat session.
• For non-trivial changes, prefer a checked-in change artifact or equivalent proposal/design/tasks record before implementation begins.
• Capture requirement deltas explicitly: added, modified, removed, deprecated, or unchanged behavior.
• Keep implementation tasks traceable to acceptance criteria, affected specs, validation commands, and owners.
• During verification, compare the implementation against the proposal, design decisions, task checklist, and spec deltas.
• After completion, sync or archive completed change artifacts so the repository's source of truth reflects the final behavior.
• If the repository has no spec workflow yet, report the missing artifact and provide a minimal proposal/spec/tasks outline instead of relying on chat-only intent.

Skill-Specific Review Scope

• README, architecture docs, ADRs, API docs, setup guides, and examples.
• Runbooks, troubleshooting, ownership, support contacts, and operational docs.
• Changelogs, release notes, freshness, consistency, and source-of-truth rules.