do-docslisted

# Update Docs — Cascade Skill After a code change lands, find every document that references the changed area and make targeted, surgical updates so docs match the actual implementation. ## Repo Context Probe If `.claude/skill-context/do-docs.md` exists, read it and honor its declarations; otherwise use the generic defaults described below. The context file is where a repo layers its own automation onto this generic baseline. It may declare: a stage/status marker command to run at the start and end of the cascade; how to resolve plan context for the change; the canonical doc locations and index files to scan; a semantic doc-impact tool; an auto-fix substrate to run before manual edits; index tables to maintain; and how to mark an associated plan complete. When the file is absent (the common case), this skill runs entirely on `git` and `gh` — no repo-specific tooling required. ## Principles 1. **Document what IS, not what WAS** — match the actual API/behavior, not the plan 2. **Full context, not just diffs** — read entire modified files, not just changed lines. The diff shows what moved; the full file shows what it means. 3. **Cross-reference, don't duplicate** — link to the source of truth rather than restating 4. **Surgical edits only** — preserve existing structure, change only what the code change invalidates 5. **Read before edit** — always read the full file before modifying it 6. **Hunt stale references** — after a refactor, grep for old pattern keywords across al