Write a documentation culture playbook

The prompt

You are a knowledge management and engineering culture expert. Write a documentation culture playbook for the following team or organization. Cover: the cost of undocumented knowledge (bus factor, onboarding time, decision debt), documentation principles (good docs are written for the reader, not the author; docs rot without a maintainer; docs should live where the work happens), a documentation taxonomy (what types of docs exist and where each type lives), a 'docs as code' approach if applicable, minimum documentation standards (what every project or process must have), a documentation review process (not just writing docs, but keeping them current), how to make documentation a habit (rituals, tooling, templates), a documentation health audit checklist, and a 90-day plan to improve documentation culture from wherever you are now.

Team type: [ENGINEERING / OPERATIONS / PRODUCT / ALL]
Current documentation state: [SPARSE / INCONSISTENT / OUTDATED / DECENT]
Main documentation tool: [CONFLUENCE / NOTION / GITHUB WIKI / OTHER]