What problem does it solve? Documentation and code comments often become stale, duplicate existing content, or confuse new readers with time-dependent phrasing and unexplained jargon. This Skill provides a structured checklist workflow that keeps Markdown docs and code comments accurate and readable for readers months later. ## Core Features & Use Cases - Four-phase writing workflow: Identify the reader and purpose before writing, apply Evergreen/Why-First/SSOT/Reader-Friendly principles while writing, then run three self-check rounds after writing. - Time-dependent expression detection: Uses grep patterns to find phrases like "currently", "previously", PR numbers, commit SHAs, and author names, with a rewrite table for replacing them. - SSOT enforcement: Checks for duplicated information across files with grep and converts duplicates into references. - Use Case: When asked to update a README, add a design doc to docs/, or write JSDoc for an exported function, the Skill walks through pre-writing planning, principle-aware drafting, and post-writing lint verification. ## Quick Start Use the evergreen-writing skill to review and rewrite this README so it contains no time-dependent expressions and follows the why-first principle.
