Write technical documentation for [SYSTEM/PROCESS/API/TOOL]. Audience: [ENGINEERS/END USERS/INTEGRATION PARTNERS]. Format: [REFERENCE DOC/GUIDE/RUNBOOK/SPEC]. Scope: [DESCRIBE WHAT NEEDS DOCUMENTING].
Documentation structure: 1) Overview (what this is, what problem it solves, who it's for), 2) Prerequisites and requirements (exact versions, dependencies, access needed), 3) Getting Started (fastest path to working — hello world equivalent), 4) Core concepts and mental model, 5) Reference section (complete parameter/config documentation), 6) Common use cases with examples (copy-pasteable code where applicable), 7) Troubleshooting guide (top 10 errors and fixes), 8) FAQ, 9) Changelog. Rules: every example must be correct and runnable. Docs that can't be followed are worse than no docs.