What problem does it solve? Documentation, READMEs, RFCs, and PR descriptions often end up wordy, ambiguous, or inconsistent, forcing readers to reread sentences to extract meaning. This Skill applies concrete plain-English rules and document structure patterns so developers and maintainers understand the text on the first read. ## Core Features & Use Cases - Plain English Rules: Cut filler words, use real symbol and path names, keep one name per concept, and prefer short ordinary words over jargon. - Four Document Modes: Choose between tutorial, how-to guide, reference, and explanation modes (based on Diátaxis) so each document has one clear purpose. - Sentence and Structure Guidance: Write active-voice instructions, organize headings for scanning, and format lists, links, and code spans consistently. - Review Checklist: Verify mode clarity, consistent naming, current paths and commands, and scannable headings before finishing. - Use Case: When drafting a README for a new CLI tool, apply the how-to guide mode with command-style instructions and real flag names so users can complete setup without guessing. ## Quick Start Use the technical-writing skill to review and rewrite my README.md so it follows plain English rules and a single clear document mode.
