Developers don't read documentation — they arrive with a task, scan for the answer, and leave. Docs that aren't structured for that pattern don't get read, they get abandoned, and the next developer asks someone on Slack instead of finding it themselves. This skill writes developer documentation that actually gets used: API references structured around what developers are trying to do (not what the code does), quickstarts that reach the first working example in under five minutes, conceptual explanations that answer the 'why' without burying the 'how', and the troubleshooting section that addresses the actual errors your users hit. It works on new docs you're writing from scratch and existing docs that grew into a disorganized pile. Give it your API or system, your target developer persona, and the top three things users get stuck on; it returns documentation structured for findability and usability, not just completeness.