docs-maintenancelisted

# docs-maintenance — Documentation Maintenance Analysis ## Workflow 1. **Connect to Docsbook** — run `list_workspaces` to find the workspace, then `get_doc_graph` to get all pages with timestamps. Reindex if graph is empty or stale. 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 via `read_doc_sections` 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, use `read_doc_sections` 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. ## MCP Tools | Tool | Purpose | |------|---------| | `mcp__docsbook__list_workspaces` | Find workspace | | `mcp__docsbook__get_doc_graph` | Page list with `last_updated` timestamps | | `mcp__docsbook__read_doc_sections` | Scan content for maintenance signals | | `mcp__docsbook__reindex_doc_graph`