docs-maintenancelisted

# docs-maintenance — Documentation Maintenance Analysis ## Workflow 1. **Gather the docs** — get the list of pages in scope (with timestamps if the source provides them) and read their content. If a semantic/graph search tool over the markdown is available (self-hosted `markdown-lsp`, or a connected Docsbook workspace), prefer it — faster and cheaper than scanning files; otherwise read the files directly with `grep`/`find`. 2. **Set staleness threshold** — confirm with the user: default is 90 days for Tier 1 pages, 365 days for others. 3. **Apply checklist** — scan pages for TODO/FIXME, "coming soon", past dates, deprecated mentions, missing ownership, and pricing consistency. Run bash scripts on local repo when available for file-age and code consistency checks. 4. **Produce report** — return one JSON issue object per finding, sorted by severity. ## Guardrails - Do not run this skill on a single freshly-created page — it is designed for whole-tree audits. - Do not edit any documentation files — surface findings only. - When local repo access is unavailable, read page content through whatever doc source you have for content-level signals; note which file-age checks were skipped. - Deprecated content should NOT be removed immediately — flag for a banner + migration path, not deletion. - Confirm with the user which pages are Tier 1 before applying the stricter 90-day threshold. ## Inputs This skill needs two things, by whatever means are available: - **The list of pages i