drin-tech-writing-voice-check

Technical Writing Voice Check

Purpose

To ensure that technical documentation is helpful, professional, and consistent.

Checklist

• Clarity: Are there long, winding sentences?
• Tone: Is it confident but not arrogant?
• Structure: Is there a logical hierarchy (H1, H2, H3)?
• Accuracy: Do the code examples actually work?
• Authority: Does it provide a definitive answer or "Maybe"?

Rules

• Use active voice.
• Cut every unnecessary word.
• Every guide starts with the "Prerequisites."

---

subagents:

• technical-writer
• ux-writer