What problem does it solve? Documentation drifts out of sync with code as projects evolve, leaving stale file paths, wrong function names, and "Planned" markers on shipped features. This Skill writes and maintains documentation that is verified against the actual implementation before anything is published. ## Core Features & Use Cases - Code-Verified Documentation: Reads implementation files first, then documents real function names, paths, and signatures instead of guessed patterns. - Structured Writing Patterns: Enforces actionable-over-descriptive style, anti-patterns-before-patterns sections, quick-reference tables, and concise code examples. - Drift Repair Workflow: Provides a checklist for comparing existing docs to code, removing outdated status markers, and fixing broken links. - Use Case: After shipping a new rate-limiting utility, ask the Skill to document it — it reads lib/security/rate-limit.ts, writes accurate usage examples, and updates related docs and indexes. ## Quick Start Ask the assistant to document a newly implemented utility or update an existing doc that has drifted from the current code.