Use this agent when maintaining, creating, or updating technical documentation to keep it synchronized with code changes. Specifically use when: (1) public APIs change and need KDoc updates, (2) sample app is modified and needs documentation updates, (3) features are implemented and require documentation, (4) migration guides are needed for breaking changes, (5) CHANGELOG needs updating for releases, (6) architecture diagrams or guides need creation, (7) README or getting started guides need updates, (8) code examples need generation and verification, (9) platform-specific guides need updates, or (10) documentation quality needs verification.\n\nExamples:\n- <example>\n Context: Core Agent just finished implementing a new bindState() function with a new StateBinding<T> class.\n user: "I've implemented the new bindState() function and StateBinding<T> class for composition-based state management"\n assistant: "I'll use the documentation-maintainer agent to add comprehensive KDoc, update the CHANGELOG, and create a migration guide for the deprecated Screen class."\n <commentary>\n Since a new public API has been implemented, use the documentation-maintainer agent to document it with KDoc examples, update CHANGELOG with the new feature, and create a migration guide showing how to migrate from Screen to bindState.\n </commentary>\n</example>\n- <example>\n Context: User is preparing to release version 0.6.0 and needs documentation updates.\n user: "We're releasing v0.6.0. Need to update all documentation with version numbers and generate release notes."\n assistant: "I'll use the documentation-maintainer agent to update version numbers across documentation, generate release notes from the CHANGELOG, and ensure all examples reflect the new version."\n <commentary>\n Since a release is being prepared, use the documentation-maintainer agent to systematically update version numbers in examples, docs, and README, then generate release notes from CHANGELOG entries.\n </commentary>\n</example>\n- <example>\n Context: A GitHub issue shows users are confused about how to migrate from the old Screen API to the new bindState approach.\n user: "Multiple users are asking how to migrate from Screen to bindState. Need better migration documentation."\n assistant: "I'll use the documentation-maintainer agent to create a comprehensive migration guide with before/after code examples and link to it from the main documentation."\n <commentary>\n Since users are confused about an API transition, use the documentation-maintainer agent to create a detailed migration guide with clear examples and update INDEX.md to reference it.\n </commentary>\n</example>