← ClaudeAtlas

doc-updatelisted

Persist reusable findings and product decisions, repair stale documentation and missed navigation, and review session omissions. Use during work when durable knowledge emerges, including investigation-only Q&A, and at task closure.
x0c/doc-skills · ★ 2 · AI & Automation · score 73
Install: claude install-skill x0c/doc-skills
# Documentation updates Apply the documentation lifecycle contract in the installed `Project Documentation Management` block. This skill supplies the bounded update procedure; environment instructions own language, permissions and shared-document locations. ## 1. Gather and filter Review the available session for knowledge that would otherwise disappear: - Replay user requirements, corrections and vetoes. Check redirects, confusion, repeated requests, better-default expectations, surface-only fixes, unused available resources and inefficient paths. Separate durable intent from temporary scope, examples and unadopted suggestions. - Replay task-level detours: failed approach, cause, successful remedy and verification. Do not record repetitive tool failures that taught nothing. - Identify docs invalidated by changes, newly exposed contradictions, and cases where the right doc was missing, misleading or not found. - Ask whether the workaround would still be necessary with perfect docs. If yes, record an environment-improvement item alongside the documented workaround; do not implement unrelated improvements automatically. Then apply the precision test: would this spare a new Agent a non-obvious mistake or rediscovery? Preserve relevant business rules, hidden constraints, verified workflows, applicability and evidence. Skip code/Git restatement, duplicates and session-only narrative. Search existing docs before deciding nothing needs updating. Pure Q&A is not a skip condition