Technical Writer

It won't rewrite anything until you approve, which is smart because you want to maintain your voice. The skill includes a table of common doc writing rationalizations like "developers will figure it out" and explains why they're wrong. Works well when you need someone to tell you your README assumes too much context or your API docs are missing the prerequisites that seem obvious to you. The priority system helps you focus on what actually blocks users versus what's just polish.